Developing a Plug-in for Custom API

Correct Answers: A, C and D

You can extend the Dataverse by creating the custom API that would be exposed as the messages.

There are two types of custom messages: Custom Process Action and Custom API.

The Custom Process Actions messages are the no-code option that you can create using the Workflow Designer.

The Custom API provides the capabilities of code extending beyond the Workflow.

You can use the maker portal, Web APIs, or the Organization service to create the Custom API.

The Custom API data is saved in the Dataverse tables.

You can invoke the custom message by using the Web API, Organization services, and plug-in.

Option A is correct because you need to know the message name, the names and properties of the message parameters, and the response properties for creating a plug-in for the custom message.

Option C is correct because after the assembly registration, by using the Dataverse Plug-in registration tools, you need to add the assembly to the solution.

Option D is correct because you need to know the message name, the names and properties of the message parameters, and the response properties for creating a plug-in for the custom message.

Option B is incorrect because you don't need to register the step for the plug-in.

You just need to register the plug-in's assembly and add it to the solution.

For more information about the Dataverse custom messaging, please visit the below URLs:

When you create a Custom API message in Microsoft Power Platform, you can develop a plug-in that can handle the message. A plug-in is a custom code that runs in response to an event in the platform, such as the creation or update of a record. Here are the correct statements about the process of developing a plug-in for a Custom API message:

A. You need to know the message name To create a plug-in for a Custom API message, you need to know the name of the message. This is the name that you gave to the message when you created it in Power Platform. The message name is used to identify the message that the plug-in will handle.

B. You need to register the plug-in for a step To register the plug-in, you need to use the Plugin Registration Tool, which is a tool that is included with the Power Platform SDK. You will need to specify the message name, the entity that the message is associated with, and the step that the plug-in will handle. The step is the specific event that the plug-in will respond to, such as Pre-Validation or Post-Operation.

C. After registration, you need to add the assembly to the solution Once you have registered the plug-in using the Plugin Registration Tool, you need to add the assembly that contains the plug-in code to your solution. The assembly is a compiled .NET class library that contains the plug-in code.

D. You need to know the names and types of the API parameters. The Custom API message that the plug-in will handle may have parameters that are passed in the request. To access these parameters in your plug-in code, you will need to know the names and types of the parameters. You can find this information in the Custom API definition in Power Platform.

In summary, to develop a plug-in for a Custom API message in Power Platform, you need to know the message name, register the plug-in for a step, add the assembly to the solution, and know the names and types of the API parameters.