Skip to main content

Async Plugins vs. Power Automate Flows

Post a Comment

CRM 2016: Solution import: Cannot delete an active workflow definition.

When you upate an exisiting solution in CRM and receive an error equal to this one:

16:33:07.66
{793dab2e-c2a4-e611-8102-c4346bad41fc}
General SLA
Failure
0x8004500F
Cannot delete an active workflow definition.

This means there is an SLA record in the system which has the status "Active".
You first need to deactive that SLA record prior to importing the solution update.
Labels:

Comments

  1. TinoDecember 1, 2016 at 9:44 AM

    Thank you for that very good tip, it saved a plenty of my time.

    Here is another Tip: If there are enabled Record Creation and Update Rules, you also have to deactivate them before you import the solution update.

    By the way: do not forget to reactivate them after solution import.

    Have a nice day!

    ReplyDelete

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

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