PL 400 : describe the plug-in execution pipeline (Create a plug-in)
Data is the key component in the modern business and technology world, always finding a new technology for the storage and analysis process. Dataverse is one of the modern cloud storage service that provides secure data storage with logic and validation mechanism to prevent duplicate and unprocessed data and improve data quality.
In other words, Dataverse is a cloud based storage service that use to securely store the business application data. Power apps and Dynamics 365 business application reside on the Dataverse and use it as storage and take advantages of rich server-side logic and validation to ensure data quality. With No/Low code, it also provides the extend the behavior of data platform. Plugin is developer tool which empower the developer to extend/modify the standard behavior.
When the declarative process of Dataverse does not provide a suitable business solution, the Dynamics Plugin is the appropriate way to modify the behavior according to the business needs. The plugin in Dataverse is a solution aware component and technical skills are essential for the development of this component. However, for the configuration of the plugin, the plugin registration tool is required, deploying to another environment, developers can use the solution.
A plugin is a .NET assembly or managed code class that registers when specific events occur. Microsoft provides a framework to extend the default behavior of the Microsoft Dataverse, called the Events Framework. This framework provides the ability to register custom code to run in response to specific events where the entire event process is executing pipeline-wise. At a high level, there are three levels involved in handling events:
- It must subscribe to a specific message that represents the type of operation.
- It must be registered in the event pipeline where it needs to be executed.
- It needs to indicate the execution mode either it runs synchronously or asynchronously.
Comments
Post a Comment