The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Like plugins, real-time workflows are executed before (pre-operation) or after (post-operation) the core operation. Both are executed inside the same database transaction.
Here are outlined some actions I have executed in order to evaluate their execution order:
Then after created and Entity A record, updated its name to ‘Test update’ and got the following audit.
The audit record shows that:
By default: real-time workflows run before than plugins for both pre and post events.
This is explained by the default value of execution order which Plugin Registration Tool sets when registering a plugin step which is equal to one.
The execution order defined on Plugin Registration Tool set the Rank property of the sdkmessageprocessingstep entity that specifies the processing order within the stage.
The workflow entity stores the definition of Real-time workflows. The Rank property is not defined when they are created form the Dynamics CRM, although there is the possibility of updating it through SDK.
If the Rank is not defined then these events are executed first. If the Rank is defined then events with lower rank are executed first.
Then I updated the execution order (the Rank property) of both plugin steps to zero without updating the Rank of workflows. The audit record shows that the plugins steps run before than workflows.
Finally I set the execution order according to the next table:
Business Applications communities