We will learn about the plugin execution pipeline in Microsoft Dynamics 365 CRM. Before we start, click here to understand the detailed concept of plugins in Microsoft CRM.
What is Plugin Event Execution Pipeline?
In Microsoft CRM, every performed action denotes an event. These actions performed in CRM are handled by Organization Web Service, which is essential part of Dynamics server. The out-of-the-box plugin event execution pipeline allows you to configure the logic in the event the plugin code will execute.
The Dynamics CRM event processing sub-system executes plugins based on a message pipeline execution model. The message or action constitutes of business entity information and core operation information, the message is passed through the event execution pipeline to execute the logical operation which resides in the particular plugin.
Event Pipeline Stages
|Event Name||Stage Name||Stage Number||Description|
|Pre-Event||Pre-validation||10||Here the plugins get execute before the main system operation. Plugins registered in this stage may execute outside the database transaction.
Security Note :- The Pre-validation stage occurs prior to security checks being performed to verify the calling or logged on user has the correct permissions to perform the intended operation.
|Pre-Event||Pre-operation||20||Here the plugins get execute before the main system operation. Plugins registered in this stage are executed within the database transaction.|
|Platform Core Operation||MainOperation||30||No custom plug-ins can be registered in this stage. It is for internal use only which is managed by Microsoft.|
|Post-Event||Post-operation||40||Here the plugins get execute after the main operation. Plugins registered in this stage are executed within the database transaction.|
Thus, we learned the detailed structure of plugin event execution pipeline.