How to handle unwanted succesive nested "apply to each"

[Julianveda]

Hi Community,

I have a flow to send specific lines from an Excel table to another Excel table and it works alright. However, I wanted to ask you about something related to the automatic insertion of "apply to each" step in my flow. For the example below I have found a way (a workaround) to handle this, but for big datasets the situation might be more tricky:

Originally, I use one single "apply to each" where I put the body from the "filter array". However, as soon as I begin to fill in the columns in the "add rows to table"  (headers in this example), there is an automatic unwanted "apply to each" that appears. Here what I do is inmediately drag the nested "apply to each" and drop it just after the "filter array" and then keep on completing the column headers and then only at the end change "value" back to "body" (coming from "filte array). 

nb. to drag and drop the nested "apply to each" I should not way too long because from at certain point I cannot any longer take that nested "apply to each" out and get this the error instead: 

another way I have found to prevent the unwanted nested "apply to each" is let "value" in the first "apply to each" step, complete my columns in the "add row into a table" and only at the end just before saving and using my flow change "value" to "body" (from the filter array). The problem here is that if at any point I have to modify my headers, a nested "apply to each" will appear which will be impossible to correct and will have to start evrything again (that's why i say that this workaround is not efficient for big datasets).

Therefore, I would like to ask if anyone know other ways to handle this problem either by preventing automatic insertion of "apply to each" or by beign capable of unnesting them once they appear.

Thank you.

Julian

[v-mengmli-msft · Accepted solution]

Hi @Julianveda ,

This is because you are using dynamic content from "list rows in a table". It can't be avoided if you use this dynamic content.

Unless you actually want to add the results of filter array to the table. Then you just need to use expressions.

Best regards,

Rimmon

[Julianveda · Accepted solution]

@v-mengmli-msft ,

Thank you for your answer. This is indeed one possible solution.

A second workaround would be to modify the json code of the workflow which also worked

Finally, a third possibility, the one that allows me to be faster for big datasets, is to create a flow leaving "value" in the "apply to each" and filling the dynamic content for all the columns  (in the aadd rows to table) and then save this workflow as a sort of template. Then, duplicate it and in the duplicated workflow, change "value" for "body" and save this as the actual workflow I will run. In the future, if I have to make important changes (and to avoid the nested apply to each), I can work on the template and then repeat the duplication process.