Skip to main content

Async Plugins vs. Power Automate Flows

Post a Comment

Async Plugins vs. Power Automate Flows

Choosing Your Automation Tool

Choosing the right tool for automation and business logic in the Power Platform and Dynamics 365 is crucial for building scalable, maintainable, and performant solutions. Both asynchronous plugins and Power Automate flows can execute logic in the background, but they are designed for different scenarios and user profiles. This interactive guide provides a comparative overview to help you determine the most suitable option for your specific requirements.

At-a-Glance Comparison

This chart provides a visual summary of the relative strengths of each tool across key decision factors. Hover over the points for more details.

Interactive Criterion Explorer

Select a criterion to see a direct, side-by-side comparison. This helps in focusing on the factors that matter most to you.

Asynchronous Plugins

Power Automate Flows

Full Decision Matrix

For a comprehensive overview, you can view the complete comparison table.

Summary & Recommendations

When to use Async Plugins

Plugins are the preferred choice for performance-critical, complex business logic that operates exclusively within Dataverse and must be part of the platform's transactional pipeline. They are a powerful tool for professional developers extending the core functionality of the platform.

When to use Power Automate

Flows excel in scenarios that involve integrations with other applications and services, scheduled automations, and empowering non-developers to create their own automations. Their strength lies in versatility and ease of use for tasks that span beyond Dataverse.

Labels:

Comments

Post a Comment

Popular posts from this blog

Yet Another Address Autocomplete PCF Control–powered by Bing

In this blog post I will not go into detail in how to install all the pre-requisites that are required to build and run PCF controls. My goal was to build a new PCF control and get into coding of PCF controls as fast as possible. Here are a few links to articles that will help you installing the pre-requisites (Microsoft PowerApps CLI)  https://docs.microsoft.com/en-us/powerapps/developer/component-framework/get-powerapps-cli Other good references to get into this topic: https://toddbaginski.com/blog/how-to-create-a-powerapps-pcf-control/ https://docs.microsoft.com/en-us/powerapps/developer/component-framework/create-custom-controls-using-pcf I looked through the Guido Preite’s https://pcf.gallery/ which will help you find appropriate use cases / examples for your own needs. It did not take very long to find a simple example to start with: Andrew Butenko's https://pcf.gallery/address-autocomplete/ A few moments later I had the idea to create yet another address autocomplete...
16 comments
Read more

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.
Post a Comment
Read more

XrmToolBox: AutoNumberUpdater - new StateCode filter

Mayank Pujara's AutoNumberUpdater plugin for the XrmToolBox is a great tool to add missing auto number values to an auto number field for an entity/table. In his blog you can find more details about the original version of his plugin: https://mayankp.wordpress.com/2021/12/09/xrmtoolbox-autonumberupdater-new-tool/ For my purposes I had to update accounts with missing account numbers, but in my use case this should only be done for those accounts that have the status value "Active".   As this plugin did not have this feature I quickly implemented it and Mayank merged my changes to his plugin source code. You can download the new version 1.2024.0.1 in the Tool Library of the XrmToolBox.
Post a Comment
Read more