Skip to main content

Dataverse/Dynamics 365 Custom API

 Understanding Dataverse/Dynamics 365 Custom APIs

Dataverse/Dynamics 365 Custom APIs serve as a bridge between the Dynamics 365 platform and external applications. They enable developers to create their own endpoints, defining the input parameters, output format, and authentication methods. By doing so, businesses can connect their Dynamics 365 environment with a plethora of external resources, ranging from third-party software to IoT devices.

Key Benefits

  • Tailored Solutions: Custom APIs allow organizations to design solutions that precisely align with their unique requirements. Whether it's fetching data from a specific source or triggering specific actions in external systems, businesses can tailor their Dynamics 365 environment to their exact needs.
  • Enhanced Integration: Dynamics 365 Custom APIs facilitate seamless integration with third-party applications and services. This integration is crucial for businesses relying on diverse tools to manage different aspects of their operations. By bridging these gaps, businesses can ensure a smooth flow of information across their ecosystem.
  • Improved Efficiency: Automation is at the heart of Dynamics 365 Custom APIs. By automating repetitive tasks and integrating various processes, businesses can significantly improve efficiency. This, in turn, leads to optimized workflows and more productive teams.
  • Data Accuracy: Custom APIs enable real-time data synchronization between Dynamics 365 and external systems. This ensures that businesses always have access to the most recent and accurate data, empowering them to make informed decisions.

Create a Custom API Definition:

  • After registering assembly, you can create Custom API with
  1. Plugin registration tool
  2. Solution
  3. Visual Studio Power Platform Tool
Here is a sample with Power Platform Tool
Sample of Parameter Request and Response

Test your Custom API with Postman




Labels:

Comments

Post a Comment

Popular posts from this blog

How to use Formatted Values in Power Automate Flow Dynamics 365

  How to use Formatted Values in Power Automate Flow Dynamics 365   If you have been working on Power Automate for Dynamics 365 you might have been wandering how you can access a lookup Formatted Value or Option Set formatted values. You can use the following format to access: body(‘{Action Name}’)?[‘{fieldname} @OData.Community.Display.V1. FormattedValue’] You just have to be mindful in Dynamics 365 lookup field name they do not translate to the proper field name, you might have to and an “_” as a prefix and “_value” as a postfix, I will leave that to you.
Post a Comment
Read more

Azure DevOps Fork Repos between two Organization

  Azure DevOps Fork Repos between two Organization This weekend I embarked on a topic a bit foreign to myself, on the surface seemed a bit simple. The idea is to fork my Azure DevOps Repo to a different organization and push changes between them. Bad news DevOps doesn’t allow to fork Repos to a different organization, you have only the capability to fork to a different Projects within the same Organization. I’m pretty much sure there are so many other ways to solve this issue, but this is the one that I found to be easy to implement. Import Repo to the new Organization Remember here you have to generate a personal token to be able to import the Repo you have to be a member of the new organization as well This might take a few minutes depending on the size of your project, once its complete you will receive a confirmation email, or just refresh it after few minutes So far all looks good, you can clone the solution in your new Organizati...
5 comments
Read more

XMLHttpRequest vs Xrm.WebApi

  XMLHttpRequest vs Xrm.WebApi If you have written JavaScript code for Dynamics 365 you have seen the use of XMLHttpRequest or Xrm.WebApi to make server-side calls. The question is which one is the right one to use? So, let’s analyze the two types of calls. XMLHtttpRequest 1.        Synchronous a.        Sample Code var req = new XMLHttpRequest(); req.open("GET", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/accounts", false ); 2.        Asynchronous a.        Sample Code var req = new XMLHttpRequest(); req.open("GET", Xrm.Page.context.getClientUrl() + "/api/data/v9.1/accounts", true ); So, passing true parameter is going to make asynchronous call while passing it false is going to make a Synchronous call. Xrm.WebApi 1.        Asynchronous a.        There is...
4 comments
Read more