PL 400 : design and develop a plug-in (Create a plug-in)

Plugin is a managed code class that runs under the Event Execution Pipeline. Under the pipeline, the developer can manage the entire behavior of the platform as it includes the entire process data of the execution pipeline. If it is well written, the performance of the plugin is optima. The developer can leverage the org service and the external service in the code. The plugin is powerful and most productive. However, to write plugin code, the developer needs special skills and knowledge. A poorly written plugin can have a significant impact on platform performance.


Basically, a plugin is just a .NET assembly that is implemented as the IPlugin interface, which can be found in the Microsoft.Crmsdk.CoreAssemblies NuGet package. The IPlugin interface exposes a single method, Execute, where we can place any custom logic.

Use Plugin when a declarative process doesn't our requirement.

Whenever a plugin is run, a stack of data is made available by the Microsoft Dataverse that contains information about the context in which the current operation resides. This plugin does business logic through an execution pipeline. Pipeline stages are selected according to business requirements or purposes.

IPlugin: IPlugin is important component for plugin design, It provides only one method, name Execute where developer can inject their business logic.

IServiceProvider:A container for service objects. Contains references to the plug-in execution context (IPluginExecutionContext), tracing service (ITracingService), organization service (IOrganizationServiceFactory), and notification service (IServiceEndpointNotificationService).

IPluginExecutionContext: IPluginExecutionContext provides access to the context for the event that executed the plugin.

GetService:The GetService method of this interface obtains the object that provides the service.

Summary:

A plugin is mandatory logic that should be used when a declarative process, such as a business rule, flow, or workflow, does not meet our requirement. Creating and maintaining plug-ins requires specialized skills of the developer. Developers are expensive and many businesses do not have access to one when needed. Business processes can change rapidly and providing options to enable change without the need for a developer can allow systems to adapt more quickly. A poorly written plug-in environment can have a significant impact on performance of platform. 

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