Can I get index number in apply to each?

[Anonymous]

Hi,

      How can I get show no in action "Apply to each".

      I want to get no for send loop email such as.

            No. 1 is xxxxxxxxxx

            No. 2 is yyyyyyy

Thanks in advance.

Aor.

[v-alzhan-msft · Accepted solution]

Hi @Anonymous ,

Please refer to screenshot below to create the flow:

Best regards,

Alice       

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi,

        Solution is create outside variable and it can not get loop no in action "Apply to each".

Thank you very much for your information.

Aor

[v-alzhan-msft]

Hi @Anonymous ,

Have you take a try with the solution?

Best regards,

Alice       

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi,

        This solution is working but I find out for other solution.

        Do you have any idea for get index no in loop not declare variable ?

Thank you very much for your support.

Aor.

[v-alzhan-msft]

Hi @Anonymous ,

There is no any other solution.

Best regards,

Alice       

Community Support Team _ Alice Zhang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[Anonymous]

Hi Alice,

        I accepted this solution.

       Thank you for your information.

Aor.

[Anonymous]

The suggested solution does not work inside an apply-to-each loop with concurrency set.  I can navigate through the index in the run log and see the data associated with each item, so the index should be possible!  When implementing the suggested solution the index count in the variable does not match the index of the run log.  The test I ran suggest it is randomly off the mark.

[HEATFreight]

This really ought to be possible without a variable! For instance, iterationIndexes() works in a Do Until loop. Why can't that same thing work in an Apply to Each loop?

Power Apps devs should fix this, as it's a sorely needed feature!

[antc2]

Here is a solution for concurrency

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

[HEATFreight]

Sorry to be blunt, but that tutorial sucks. It doesn't specify what the 'Apply to each' is operating on. What's the input to the loop? It's unclear how that solves the problem.

Of course, if you add a unique integer ID to each element in an array, then you can use that as an index. That's an obvious workaround for iterationIndeces() not working in 'Apply to each' loops, but it's not without faults: namely that you must add unnecessary logic to the flow and that you must iterate through the entire list of data to assign unique integer IDs to each element.

This may be prohibitively intensive, computationally, when working with large sets of data. But any additional delay in run time is undesirable.

However, upon taking a second look, I believe I understand. The 'Apply to each' must be iterating on the 'IDs' array, rather than the original data in the 'Compose' array. This solution seems workable, assuming the range() function does not take a long time to count the length of the input array, and I'm guessing it's pretty fast because it's not really iterative like a single-concurrency 'Apply to each'. A normal workaround would involve preemptively adding ID integers to each element in the array with an iterative loop, but this solution only iterates once, and it can do so concurrently, because it's not iterating on the input data, but on the range() array, and selecting indices from the input data using the current value of the range() iteration.

Pretty smart actually. Still think they could have done a better job of documenting it, because I doubt most folks will stare at that tutorial, scratching their head in confusion, long enough to understand the crucial missing piece of information: the input to the 'Apply to each'!

Thanks @antc2 

[HEATFreight]

@v-alzhan-msft There is always another solution, especially so for problems where people say there isn't one.

[akleinvm1]

Another way would be to add an index field before the apply to each. You can use this trick:

range(0, length(outputs('Compose')))

addProperty(outputs('Compose')?[item()], 'Index', item())