Skip to main content

How to call Dynamics 365 Action from Logic App.


How to call Dynamics 365 Action from Logic App.


You might have stumbled in a scenario where you have an Action in Dynamics 365 and you want to trigger it from a Logic App.

As you know the Dynamic 365 Connector has good features, but it does not have the ability to call an Action at least as far as I know.

You can solve this by leveraging the HTTP call in logic App, to have a better understanding you can read on the following article
https://docs.microsoft.com/en-us/azure/connectors/connectors-native-http.

So the idea is to create a Rest API call that triggers the Dynamics 365 Action.
Prerequisite:
  1. Generate your REST API call
    1. You can use CRM REST Builder
    2. In general though this is the generic path to call an action {{clientUrl}}/api/data/v9.1/{{Entity Name}}({{Record Guid}})/Microsoft.Dynamics.CRM.{{Unique Name of Action}}
  2. Get the following information for Active Directory OAuth authentication
    1. Tenant ID
    2. Audience which is the Client URL
    3. Client ID
    4. Secrete Key

Once you have these information you just have to create an HTTP Action you can refer the following Image



Happy Coding :)

Comments

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.

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...

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...