Iteractive Macro logic help

[MarkGi]

Hi 

I am looking  at a colleagues workflow to see if there is the possibility to chnage some of the workflow into an Iteractive Macro.  I looked at quite a few of the examples and videos but most seem to have only one looping feature where as I think I have 2 separate data loops needed.

This is the area that I am trying to amend:

Working from the second Filter.   

• The workflow takes the input data from the first Union and does a filter against the output of the previous Filters Right Unjoined output
• From this Filter - The joined data is then added to a new Union and the output of this Union becomes the new Left input to the next Filter and the previous Filters Right Unjoined is then the Right second Filter input. 

This continues until the Filter Join Data is empty.   When this occures the Data set in the last Union is passed on to the remainder of the workflow for further analysis.

Can anyone shed some logical light on making this loop into an Interactive macro ?    

[Hsandness]

Hi @MarkGi ,

You will want to turn all of these actions into one iterative macro. Before the entire dataset is passed into the macro, you'll want to give each record it's own RecordID column with the RecordID tool. This column helps with the iteration process within the iterative macro by doing RecordID - 1 = Engine.GUIiterationNumber on each loop through the macro. I typically set this operation in a filter tool and have it be the first tool within the iterative macro.

This is difficult for me to explain in concise detail. Are you able to share this workflow along with some sample data and the desired output?

[Qiu]

It seems to be something can be done with an iterative macro but need some sample data for input and ouput for test. 

[MarkGi]

Thanks for the quick replies, 

The Data is coming from the SAP systems which is a set of nested "folders" and "objects wtihin folders, becasue of this I dont believe that the RowID option mentioned would work as the "trigger" to end the Macro, this is because there are alway remaining rows of data in the Right UnJoin even when the Join = Empty.

Unfortunately due to company policies I cant share the workflow or the data.   I will have a look at other published workflows again and see if I can spot the logic in being able to pass 2 loops of data back through Macro.

But thanks