Today I came across a weird feature in Microsoft Flow. I collected a list of files from SharePoint and I was setting a Compose with the title of my files.
Reference Compose inside an apply to each
Table of Contents
In the run history each file was listed and I was quite happy with this. Inside the apply to each step can use this value.
But what if I use this outside the Apply to each after the Apply to each has finished. To my surprise I was getting an array back.
My first thought was: “That is annoying. That can’t be right!”
But you could use this to filter your arrays.
With the condition set to:
This now resulted in an array just giving me the files starting with the letter t.
However I found that the array returned looked like this:
It looks like the compose actions inside the apply to each steps are created as an array. Why?
Although by default the Concurrency is switched of on every Apply to each step. It is possible to enable this.
To make sure that things don’t go wrong you could switch this off, however I have found recently that the order of the items is not affected by the Concurrency feature. Performance wise the concurrency feature can really make a difference.
The advanced method
Do you want to take this method further, then read The advanced Pieter’s method in Power Automate