How to: Set Up an Integration to Microsoft Dynamics 365

This article explains how to set up an integration between Process Automation and Microsoft Dynamics 365. This makes it possible to easily get information from Dynamics 365 to enrich your process and update Dynamics 365 with data that has been enhanced through processes.  

1. Request that the support team activate Integration credentials and the Dynamics integration business component on your contract.

2. From the Space settings page, select the Integration tab.
   
   
   

3. On the Integrations page, click on the Add button under the Integration credentials section.
   
   
   

4. Fill in the Integration Credentials
   
   
   1. Credential type: OAuth 2.0
   2. Grant type: Client Credentials 
   3. Name: Name the integration.
   Required information*
   4. Auth URL: the Resource URI with appended scope (/.default)
   https://myorg.crm.dynamics.com//.default (double backslash is intentional)
   5. Client Id: The client id
   6. Secret: The secret
   7. Scope: Use this field and add the TenantId here.
   8. Resource: the endpoint (https://myorg.api.crm.dynamics.com/api/data/v9.2/), include the backslash

   * Information on how to get this information is available in Microsoft’s API documentation for Dynamics 365. We recommend you set up an App in Azure and add an app user that has the correct permissions for reading and writing data to your Dynamics 365 instance.  

    

5. The next step is to add the business component. Navigate to the Business components tab and click on Add new.
   
   
   
6. From the Business components drop-down, select Dynamics. 
   
   
7. In the Dynamics form, reuse the integration credentials by retyping the exact same name you used in Step 4 and selecting Add. 
   
   
8. The Dynamics component is now visible in Process Studio. Please see the notes below.

Please note the following:

• A form needs to exist with a designated field for specifying the Name or Id of the account in Dynamics you want to query information about. Both an Account ID (A GUID, unique identifier) and an Account Name (e.g., 'InRule') can be used to specify the name for getting information about an account.
• It is also possible to get information about Contacts. For this, the contact's ID must be used (A GUID, unique identifier). 
• For updating account data or contact data, the ID (GUID) is required. Name will not work. If the field you wish to update has a formatted value and a raw value, you must update the raw value. 
• This AccountId/AccountName field can be overwritten by a response if the field is configured in the "Fields" section rows.
• The ingoing sequence flow must be configured to "go to next task".
• A form must be connected to the component.
• A maximum of 10 rows/form fields can be populated.
• The same Dynamics field can be used multiple times for different form fields.
• If there's a "backend" value to a field in Dynamics and a Formatted value, the Formatted value will be returned by default.
• If you want the non-formatted value, add the following after the selected field: .[RawValue]. E.g phone.[RawValue] 
• The requested field needs to exist in Dynamics or the business component will fail (this is implemented by Dynamics, and outside of InRule's control)
• If a row doesn't have all 3 properties set (Field name in Dynamics, Data object, and Form field name), that row mapping will be ignored.