Iterative macro

[rjadia]

Why is iterative number resulting into null on a nested iterative macro?

[alexnajm]

Without seeing any configuration, it's hard to advise. Best guess is that you are not passing your iteration number from your first macro into the nested macro

[OTrieger]

@rjadia 
I agree with @alexnajm.

Additional data will help.

But what you can do run your first iterative macro and see if you are the desired result. If all working well, try the 2nd iterative macro, not nested, to see if you are getting the desired result. If both working well, then something is not configured correctly when you are nesting the 2 macros.

[OTrieger]

But without data is very hard to tell, it is more guessing.

[rjadia]

Thanks... let me try

[rjadia]

The macro when run independently gives the result as needed. but when I nest them, the error happens on the macro, not in the nested one, with a null value. see the attachment.  "steps" is driven by "iteration" and is the nested macro and "level" is driven by "Iteration0". Iteation0 results into null value after first iteration. see the attached picture.

[apathetichell]

hard to tell without seeing your workflow/data - but I'd see if perhaps the inner iterative macro isn't being triggers for some data. That would mean that it flows directly to your output from the outer macro. in a union all fields configuration this value would be null because the inner macro would not run -> and no value would exist for this field.

that's where I'd look without seeing anything of your data/workflow.