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

The great power of Microsoft Dataverse is extensibility which makes it more user and business friendly. Extensible code allows us to add new feature by adding new business logic. Makes the implementation of the REST API in the Dataverse more flexible and extensible. Automation of business logic and integration with other systems are driven by Events.


The event framework provides the capability to register custom code to be run in response of specific event : Microsoft

To take advantage of the Events Framework in the Microsoft Dataverse, we need to understand about the available events and their processes. Data operations with events adds more efficiencies for developers to use resources to make sense of business operations, but this needs to be understood about time limits and constraints, as some processes are short-lived and impactful enough for applications which could be caused of poor performance for applications.

To use of Dataverse Custom API, developers can create the custom events. Each custom API will create a new Dataverse message and provide the web service endpoint to call the custom API. Although, Custom action process and Custom API provide to create new API. Custom process action provides a no code way to include custom message.
Custom APIs are an alternative of Custom process action. It provides capabilities specifically for developer to define their logic in code with more options.

To create Custom API: 


We need to set this for each Custom API, Request Parameter, and Response Property individually.

 New Custom API Form:

Binding is an OData concept that associates an operation to a specifics table and there are three type of Binding in Custom API.

Binding Type:

Is Function Property:

This property defines that whether Custom API is function or action. 

Function: In OData a Function is an operation called using HTTP Get request which returns data without making any changes. all the parameters are passed as parameters in the URL when invoking the function.

Action: Action performs the same opertion passing all the parameter data in the body using POST request.

Is Private Property:

The Is Private property will block the Custom API from appearing within the $metadata service document and prevent Dataverse code generation tools from creating classes to use the messages for your Custom API.

Enabled for Workflow: It should be true when Custom API will call from workflow, but Is Function Property should be false.

Allowed Custom Processing Step Type:


Plugin Type: To specify main operation logic with register the plugin step.


Comments

Post a Comment

Popular posts from this blog

Exploring the Differences: Managed vs. Unmanaged Solutions in Dynamics CRM/Dataverse

Image
In Dynamics CRM/Dataverse, solutions are central to Application Lifecycle Management (ALM) , providing a structured way to manage, package, and distribute customizations across environments. Microsoft uses solutions to transfer apps and customizations by exporting them from one Dataverse environment and importing them into another.  Each solution is authored and maintained by a publisher and includes components like Power Apps (canvas and model-driven), flows, entities, forms, connectors, web resources, and configurations—excluding business data. Solutions streamline ALM practices within Microsoft Power Platform. In Dynamics CRM/Dataverse, there are two types of solutions: Managed and Unmanaged . When planning an implementation, it’s important to understand the advantages and disadvantages of each to make an informed decision. Let’s explore both types to determine the best approach for development and deployment. In Dynamics 365 CRM, a managed solution is a fully packaged solution ...
Read more

PCF vs. Web Resources: Choosing the Right Extensibility Tool for Dataverse

Image
Extensibility refers to the ability to be extended or augmented beyond the default capabilities of the platform. This involves customization but also includes more advanced techniques, such as coding, integration with external services, and the use of custom components. In the context of Power Platform and Dynamics CRM, the term "extend behavior" refers to the ability to customize and extend the functionality of the platform to meet specific business needs. Extensibility often requires technical skills, such as coding in JavaScript, C#, or using tools like Azure Logic Apps and Power Automate for complex integrations. Customization  is a subset of extensibility. Customization involves configuring and modifying existing elements within the platform to suit specific business needs. Extensibility, on the other hand, covers a wide range of functions and techniques, including customization and more advanced development and integration tasks, to extend the capabilities of the Power ...
Read more

Effective Strategies for Debugging Plugins in Dynamics CRM

Image
In a recent interview, I was asked about debugging plugins in Dynamics CRM. The interviewer specifically wanted to know my approach to plugin debugging. In response, I mentioned using the Plugin Registration Tool profiler. However, I later realized there are multiple methods to debug plugins in Dynamics CRM/Dataverse, each essential for efficient troubleshooting. Debugging plays a crucial role in development, and having a solid understanding of various debugging approaches can help streamline issue resolution in Dynamics 365. Here, I'll explore different techniques for debugging plugin code. There are below options to use in the plugin in Dynamics CRM/Dataverse ITracingService : In Dynamics CRM plugin development, ITracingService is a service provided within the plugin's execution context that logs information for tracing and debugging. It allows developers to capture real-time. Plugin Profiler : A plugin profiler in Dynamics CRM (or Dataverse) is a debugging tool in the Plugi...
Read more