Plugins in Dynamics CRM and Model-Driven Apps

Plugins in Dynamics CRM and Model-Driven Apps

In Dynamics CRM and Model-Driven Apps, plugins are custom code components used to extend platform behavior. They allow developers to enforce business rules, manipulate data, and integrate external systems. Both platforms operate on the same underlying data layer known as Microsoft Dataverse.

Dataverse stores all information as tables, including business records such as accounts and contacts, as well as system-level components like forms and views. Plugins attach logic to these tables by responding to messages generated during data operations.

How Plugins Work: The Messaging Pipeline

Whenever a user performs an action—such as saving a record—the data is packaged into a structure called the Target and sent to Dataverse. This action generates a message like Create or Update.

That message then moves through a predefined execution pipeline. Plugins can be registered at different stages of this pipeline to intercept and process the data.

Execution Stages

Pre-Operation Stage
This stage runs before data is written to the database. Plugins registered here can modify the Target directly. Common use cases include formatting values, setting defaults, or deriving field values. Since the data is altered before persistence, the database never stores the original, unprocessed values.

Operation Stage
This is the point at which Dataverse commits the data to the database. Custom logic is rarely placed here, as this stage represents the core system transaction.

Post-Operation Stage
This stage executes after the record is saved. At this point, the record has a unique identifier. Plugins in this stage are commonly used for creating related records, performing associations, or triggering follow-up logic that requires the record ID.

Development and Registration

Plugins are developed as .NET class libraries and deployed into the Dataverse environment. After deployment, plugin steps are registered against specific messages, tables, and pipeline stages. Correct registration is critical for predictable and reliable execution.

Understanding the execution pipeline is essential. Incorrect stage selection can lead to data inconsistencies, recursion, or unexpected behavior across the application.

Comments

Post a Comment

Popular posts from this blog

Part 1: Creating Code Apps in Power Apps - A step-by-step guide (with real errors I faced & how I fixed them)

Image
Intro In this post I’ll walk you through how I set up a code-based app for Power Apps (React/Vite front-end + Power Platform CLI for packaging/deployment), the exact errors I ran into, and how I solved them. If you want a hands-on, copy-paste able guide that covers Node versions, pac auth, environment issues, and packaging tips, this is for you. Prerequisites Microsoft 365 account with access to a Power Platform environment Node.js ( 20.19+  recommended LTS) VS Code Install power platform tools extension in VS Code. Steps: Step 1 : Open Visual Studio Code and launch the integrated terminal. Step 2: In the terminal, run the following commands one by one.   mkdir D:\CodeApps - Force cd D:\CodeApps npm create vite @latest myfirstapp -- -- template react - ts cd D:\CodeApps\myfirstapp npm install Initially, I ran the command: npm create vite@latest MyFirstApp -- --template react-ts This gave the error: Invalid package.json name The issue was caused because package...
Read more

Calling Microsoft Graph API from Power Automate Using Azure App Services – Step-by-Step Guide

Image
Step 1: You should have an Azure subscription, or if you have access to the Microsoft Entra Admin Center, you can create an app from there. This app can then be used in Power Automate to connect to Microsoft Graph API. Step 2: Click on "New registration" , provide a name for your app, assign the required API permissions (such as Microsoft Graph permissions), and then click "Register" to complete the app registration process. Step 3: After registration, you'll be redirected to the app's overview page. From there, navigate to the API permissions tab and click "Add a permission" to assign the necessary Microsoft Graph API permissions. Step 4: Select Microsoft Graph as the API, and based on your requirements, choose the appropriate permissions. In my case, I selected Application permissions , which do not require user sign-in and are suitable for background services or automation. Step 5: Select the required Microsoft Graph API permissions. Yo...
Read more

Step-by-Step Guide: Power Automate Custom Connector Using Graph API from Azure App Service

Image
Step 1: Open Power Automate, navigate to the Custom Connectors tab, and select Create from blank as shown in the image below. custom connector(click image for better resolution) Step 2: In the General tab, upload an icon (less than 1MB), add a description, select the correct scheme (in my case, HTTPS ), and provide the host name. For example, if your API URL is https://graph.microsoft.com/v1.0/users/{email} , the host name will be the highlighted part — graph.microsoft.com . Step 3: Go to the Security tab. Here, you need to select the authentication method. Choose OAuth 2.0 as the authentication type, as shown in the image below. Step 4: Select the Identity Provider as Azure Active Directory . Check the box Enable Service Principal Support . This option allows you to create a connection using a Client ID and Client Secret instead of using the user's own authentication. Next, provide the Client ID , Client Secret , Tenant ID , and other required details as shown in t...
Read more