Avoiding unwanted Apply To Each

[sophiad26]

Hi all,

I'm building a flow that only needs one Apply To Each action to go through an excel file. The problem is that when adding the Condition action, it would add another apply to each that I actually don't need and will cause the flow to fail. As you can see on the image below I have the 1st Apply To Each action (the one that I need) right after the Get Items, and the other one was auto-generated after adding the Control. How can I prevent this? Thanks in advance

[creativeopinion]

@sophiad26 Can you expand your condition action and upload a screenshot. The most likely reason it's nesting itself inside an Apply to Each action is that you are checking a multi-select column. 

[sophiad26]

---

@creativeopinion wrote:

@sophiad26 Can you expand your condition action and upload a screenshot. The most likely reason it's nesting itself inside an Apply to Each action is that you are checking a multi-select column. 

Hi @creativeopinion here's the condition I created

---

[creativeopinion]

@sophiad26 I would recommend using a Filter Array action in your flow to make it run more efficiently. To learn more about how to use the Filter Array action, please refer to this recent YT Tutorial I uploaded. You can reference the section that shows you how to filter by a key. 

With the Filter Array action you can evaluate all items in your SP list that meet your criteria (eg. Application equal to ___ and Amount equal to ___ ). Then add a Compose action to count items returned from the Filter Array action. This way you can stop the flow (if no items are returned) otherwise you are unnecessarily looping through each item in your list to check the conditions in your criteria. As your list grows—each flow run will take longer to run. 

Hope this helps!

If I helped you solve your problem—please mark my post as a solution ✅.
Consider giving me a 👍 if you liked my response!

👉 Watch my tutorials on YouTube
👉 Tips and Tricks on TikTok