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
Dyn365CE19 June 2024XrmToolBox: AutoNumberUpdater – new StatusCode filter
Dyn365CE8 February 2023Power Automate: SharePoint Copy file action fails on file names with a plus (+) sign- Dyn365CE25 January 2023Power Automate: Avoid Apply to Each for List rows action (DataVerse)
Dyn365CE30 November 2022Workaround for broken sort buttons on the record creation and update rule items grid
