Tip #1459: How to bypass Dataverse plug-ins and flows in Power Automate actions

The image presents an adventurous scene where an explorer, evoking a 1930s adventurer with a hat labeled "REAL DEVELOPER," stands before a tunnel entrance, suggesting the start of a journey or discovery. To the right, a signpost with the word "LOWCODE" points in the direction of the tunnel, indicating that this path is a shortcut or a more efficient route. The surrounding environment is lush and verdant, with mountains in the distance and a clear sky above. An airplane flies overhead, contributing to the sense of adventure and exploration. The overall composition of the image combines themes of old-school exploration with modern software development concepts.

When you need to insert, update, or delete a large number of records in Dataverse, synchronous plug-ins can get in the way. Asynchronous plug-ins and Power Automate flows are triggered independently (out of process) but can be overwhelming for the system and can be throttled down. Did you know you can bypass either? Did you […]

Tip #1372: Synchronous Power Automate Flow on create/update of a record

Today’s tip is indirectly from Alex Shlega. Alex is very thorough in his writing so I was a bit surprised that his answer to running a synchronous flow from a webhook was a ‘no’. The reason cited was that CDS “execution pipeline” won’t wait for the Flow completion. Well, it will indeed not, but only […]

Tip #34: CRM Gustronomy – force the workflow order

Shan McArthur, our fellow MVP, asked the other day: How can we order workflows? For example, I have an auto-number workflow that adds a case number to an entity, and I want that workflow to run before another workflow. I considered using wait states – i.e.: workflow 2 waits until the case number is not […]