Let us fetch 5000 contact records using List Rows, and then update it using Apply To Each. It took around – 37 minutes Now let us enable concurrency control for Apply To Each action, and let it run under 20 (default) degree of parallelism. This time it took around 4 minutes. Let us increase it … Continue reading “Concurrency Control – Apply to each for improving performance (Power Automate…
Continue Reading Nishant Rana’s Article on their blog
Concurrency Control – Apply to each for improving performance (Power Automate / Dataverse)
Let us fetch 5000 contact records using List Rows, and then update it using Apply To Each. It took around – 37 minutes Now let us enable concurrency control for Apply To Each action, and let it run under 20 (default) degree of parallelism. This time it took around 4 minutes.
Blog Syndicated with Nishant Rana’s Permission
More About This Author
Array
- Dyn365CE7 May 2024Use Filter Array action to remove values from an array variable – Power Automate
- Dyn365CE6 May 2024Fixed – The latitude or longitude for the User record associated with this resource is invalid – Dynamics 365 Field Service /Dataverse
- Dyn365CE30 April 2024Use Geolocation Settings for Location Tracking and Auditing – Dynamics 365 Field Service
- Dyn365CE29 April 2024Fix the trigger – Microsoft.OData.ODataException: A binary operator with incompatible types was detected. Found operand types ‘Edm.Guid’ and ‘Edm.String’ for operator kind ‘Equal’ (Power Automate / Dataverse)