Can anyone please explain why anyone would want to use plugins or custom workflows in Dynamics CRM when Power Automate is readily available? This article suggests that Power Automate provides less functionalities and is harder to debug. I suppose another detriment of Power Automate is that there is no source control and that it cannot be added to your solution. That being said, I still feel like it is far more desirable for organizations to have "citizen developers" make Power Automate flows so that they don't have to hire developers and go through the process of developing, testing, and maintaining plugin or custom workflow code.
Just to correct one misconception in the original post - your power automate flows can be packaged in your solution files, you just need to add them from within the make.powerapps interface rather than the Classic interface. In addition to packaging in a solution file with other components you can also export them in their own zip file and import them in their own zip into another instance/environment (either from Flow or if in a Solution from the Default Solution, last time I looked you couldn't do this export/import it from other solutions)
Hi Hapa1,
Power Automate in its current state does not replace the need for plugin/custom workflow developers. It cannot do everything that a plugin/custom workflow can, and it is not as concise. You can find a list of advantages that plugins have over Power Automate flows in this article.
Whether or not an organisation hires a citizen developer or a professional developer will depend on the organisation and their requirements. At the end of the day, Power Automate flows still require development, testing, and maintenance.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 291,240 Super User 2024 Season 2
Martin Dráb 230,149 Most Valuable Professional
nmaenpaa 101,156