Platform

Platform

A place for Apptio product users to learn, connect, share and grow together.

 View Only
  • 1.  Error Message - A cycle was introduced in a transform step

    Posted 12/02/21 06:48 PM
    I have been trying to figure out why I am getting this error message.  I can not seem to find anything on this in the help or Forums.  Any anyone has an idea on why this would be happening.  I am doing a lookup from one table to another using source columns.  

    =Lookup(pono,THC Purchase Order,pono,CapitalProjectNo)

    Any ideas or suggestions would be great!

    Thanks,

    Michael Enslein
    #TBMStudio


  • 2.  RE: Error Message - A cycle was introduced in a transform step

    Posted 12/03/21 02:29 AM
    Hello @Michael Enslein. Most likely you're doing a reverse lookup from THC Purchase Order to the table you're making the Lookup() you describe. If not directly, somewhere in the allocation path there is such a call.
     
    For the TBMC20 hackathon I presented a proposal that would address exactly this case (link). I need to turn it into an enhancement request.


  • 3.  RE: Error Message - A cycle was introduced in a transform step

    Posted 12/03/21 08:26 AM
    I agree.  This occurs when the source table is targeting a table that is already referencing the source table creating a circular reference.  
    I liked your video @Guillermo Cuadrado.  ​


  • 4.  RE: Error Message - A cycle was introduced in a transform step

    Posted 12/03/21 07:46 PM
    Hi @Michael Enslein,
    I suspect @Guillermo Cuadrado may be right but just to be sure, have you submitted a support ticket? You may want to get support to look at it to see if they can help identify and resolve the issue.  ​​

    ------------------------------
    Debbie Hagen
    Apptio
    ------------------------------



  • 5.  RE: Error Message - A cycle was introduced in a transform step

    Posted 12/09/21 09:14 AM
    Edited by Kyle Castro 11/05/24 05:47 PM
    Hi @Michael Enslein, in our experience, this issue tends to come up when the Lookup​ Table is also doing a lookup/lookupex into the target table (i.e. both tables are doing lookups into each other).

    One way to get around this is to create a table transform of your lookup table using the Source Data, and do the lookups into the transform:


    #TBMStudio