How to get the numbered iteration in an Apply To Each function?

[asAdmin]

I have a flow that when a sharepoint list item is created, it gets the attachments from that list item, loops over them using Apply To Each, and for each one, creates a file in a sharepoint document library. This works great, except when I get to naming the files. I can do this successfully with a static file name or a dynamic name from the list item but I am trying to name them dynamically, so that each iteration adds that number iteration to the file name. For example, if I had 3 attachments, it would name the files:

'Picture 1'

'Picture 2'

'Picture 3'

I am having trouble figuring out how to capture which iteration the Apply To Each is on, in order to append it to the file name. It either needs to keep a count during the iteration or it needs to know the total amount of attachments before the Apply To Each so I can try to attach the number that way? Any thoughts on best way to know the current iteration or a way to count through the iterations?

[asAdmin · Accepted solution]

Nevermind I figured it out. You can initialize a variable outside of the Apply to Each, then use the Increment Variable inside the Apply To Each to increment it through each iteration. Then you can set that variable into the file name.

[Anonymous]

Just found a better solution:

https://docs.microsoft.com/en-us/azure/logic-apps/workflow-definition-language-functions-reference#i...

[Anonymous]

Unfortunately, this [The function 'iterationIndexes'] does not seem to work for "Apply To Each", but only for "Until" loops. It is a weird design to have such a function only work for one of the two loop types - but here we are.

[PieterVeenstra]

Actually, there is a better solution to this problem:

First create an array with IDs and then process the IDs rather than the array of items:

https://sharepains.com/2022/08/17/avoid-variables-apply-to-each-power-automate/

[SwJ23]

I realize this post is several years old, but I want to point out (for others like myself) that the likely reason for this is that concurrency control can be enabled on Apply to Each loops, but not Do Until loops.

With parallelization, the concept of an iterator gets muddy.