PL 400 : publish an event by using the (Publish and consume events)

A plugin is a special mechanism to enhance the behavior of the Microsoft Dataverse platform. A plugin is a .NET assembly that can upload to the Microsoft Dataverse platform, but developers use a plugin registration tool to upload custom business logic and wire it up with the appropriate events (steps). The concept of plugin allows us to add  a new feature by new DLL. This plugin  works under within the event framework.
A plugin is .NET assembly that can be used to intercept the events generated from the CRM system to perform a variety of actions.




To register a plugin, we need to follow the below steps:

  • Develop a plugin event handler as a DLL assembly
  • Sign and compile the DLL Assembly.
  • Register the plugin DLL assembly in Microsoft Dataverse using the Plugin Registration Tool.
  • Register the steps of the implemented event handlers for required events using the Plugin Registration Tool.

An event, in a computing context, is an action or occurrence that can be identified by a program.

In event-driven programming, it is a paradigm where entities/objects communicate by sending messages to another through an intermediary. Using plugins, we can fire custom actions or events on any entity. It helps to integrate with Customer Engagement to modify or enhance the standard behavior of the platform. In the article, we will discuss about Plugin Registration Tool and publish an event. This tool is available on SDK folder. To use of this tool, we need to log in with appropriate credential.

To register the event in the Plugin Registration Tool:


After the selection of "Register New Step", Register new Step window will open:


General Configuration information:


Event Pipeline Stage of Execution

Execution Mode:


Deployment:



Delete AsyncOperatoin if StatusCode =  Successful :

Doesn’t create SystemJobs for async jobs which run successfully, so it assists the save  valuable storage space if the plugin is run repeatedly.

Configuration:



Comments

Post a Comment

Popular posts from this blog

Powering Up Your Analytics: Exploring Power Query in Power BI

Image
Data is a valuable asset that has a profound impact on almost every aspect of modern life. Its proper collection, analysis and application can promote innovation, improve efficiency and solve complex challenges in various sectors. In data processing, ETL is a comprehensive process that includes data extraction, transformation, and loading, while Power Query is a specific tool that facilitates the "extract" and "transformation" aspects of ETL, allowing data to be collected and analyzed. Permission is granted to process. And reporting. is ready. It becomes easy to do this. Microsoft's ecosystem of products. Power Query is a data transformation and data preparation engine. Power Query is available in Microsoft Excel and Power BI. Power Query provides a user-friendly and intuitive interface for data professionals and analysts to access and manipulate data from various sources without the need for extensive coding or scripting. It allows users to connect to a wide ra
Read more

Power App Component Overview : Canvas App vs Model-Driven App

Image
The Power Platform is a suite of low-code/No-code tools and technologies developed by Microsoft and Power App is integral component of Power Platform. Power App is platform that enables users to build custom web and mobile applications with a visual interface and minimal coding. The platform support various data sources, including Microsoft 365, Azure Service, and many other, enabling users to integrate and interact with their existing data and systems. In Microsoft's Power Apps, there are two main types of apps that we can create: Canvas Apps: Canvas apps provide a blank canvas where you can design highly customizable applications with a drag-and-drop interface.  Model-Driven Apps: Model-driven apps are built on top of the Dataverse, which provides a set of pre-built data entities and business logic. There are few key technical difference between Canvas App and Model Driven App: During the usability analysis, these high-level technical differences need to be considered. The choi
Read more

Exam PL-400: Microsoft Power Platform Developer

 Create a technical design (10-15%) Validate requirements and design technical architecture design and validate the technical architecture for a solution design authentication and authorization strategy determine whether you can meet requirements with out-of-the-box functionality determine when to use Logic Apps versus Power Automate flows determine when to use serverless computing, plug-ins, or Power Automate determine when to build a virtual entity data source provider and when to use connectors Design solution components design a data model design Power Apps reusable components design custom connectors design server-side components Describe Microsoft Power Platform extensibility points describe Power Virtual Agents extensibility points including Bot Framework skills and Power Automate flows describe Power BI extensibility points including Power BI APIs, custom visuals, and embedding Power BI apps in websites and other applications describe Power Apps portal extensibility points incl
Read more