Power Automate: Avoid Apply to Each for List rows action (DataVerse)
If you do not want to use the Apply to Each loop after a Dataverse List rows action you can use the following in a Dynamic Content / Expression box to directly use a field’s value in e.g. Compose action:
first(outputs(‘List_rows’)?[‘body/value’])?[‘apx_fullpath’]
instead of apx_fullpath you can use whatever field name you need for the entity that’s been queried before.
Continue Reading Andreas Cieslik’s Article on their blog
Power Automate: Avoid Apply to Each for List rows action (DataVerse)
If you do not want to use the Apply to Each loop after a Dataverse List rows action you can use the following in a Dynamic Content / Expression box to directly use a field’s value in e.g. Compose action: first(outputs(‘List_rows’)?[‘body/value’])?[‘apx_fullpath’] instead of apx_fullpath you can use whatever field name you need for the entity that’s been queried before.
Blog Syndicated with Andreas Cieslik’s Permission
More About This Author
Array
Dyn365CE2023.01.25Power Automate: Avoid Apply to Each for List rows action (DataVerse)
Dyn365CE2022.11.30Workaround for broken sort buttons on the record creation and update rule items grid
Dyn365CE2022.04.06How to quickly update an attibute from a browser bookmark
Dyn365CE2020.09.28How to create new (missing) columns for entities in your Data Export Service Azure SQL database
