Applies to:
Denodo 8.0
,
Denodo 7.0
,
Denodo 6.0
Last modified on: 22 Jun 2020
Tags:
Connectivity
Dynamics
OData
This document describes how to install and configure the Denodo OData 4 Custom Wrapper in order to connect to Microsoft Dynamics 365 using the OData 4 API and OAuth 2.0 authentication.
Microsoft Dynamics 365 is a product line of enterprise resource planning (ERP) and customer relationship management (CRM) applications commercialized by Microsoft. This article describes the process for connecting to the ERP module also called Microsoft Dynamics 365 for Finance and Operations.
Microsoft Dynamics 365 publishes an OData 4 API in order to be able to connect from different sources and perform operations in the server. The authentication method supported by the OData API is OAuth 2.0.
In order to connect to an OData 4 source, the Denodo OData 4 Custom Wrapper is needed. The Denodo OData 4 Custom Wrapper is a component available in the DenodoConnects section of the Denodo Support Site that provides CRUD access to your OData entities supporting OData protocol version 4.
Once the Denodo OData 4 Custom Wrapper has been downloaded, you can unzip the distribution in a known location in the Denodo server filesystem. You will find the dist folder with the jar files of the Custom Wrapper and doc folder with the documentation. For more information, refer to the Denodo OData4 Custom Wrapper - User Manual.
To import the custom wrapper, follow these steps:
1. From the design studio, go to: File - Extension management (in Denodo 6.0: Jar management)
2. Click on Import button and load the “denodo-odata-wrapper-
{vdpversion}-{version}-jar-with-dependencies.jar” file downloaded from
Denodo Support Site.
Follow the below steps to connect Microsoft Dynamics 365 from the Denodo platform:
Step 1: Register an app in Azure Active Directory
Step 2: Assign secrets for created Apps
Step 3: Get Authorization and Token Endpoints
Step 4: Obtain Access and Refresh Token using OAuth 2.0 Credentials Wizard
Step 5: Configure OData Wrapper Data Source
Step 6: Create Base Views
First of all, It is necessary to register Denodo in Azure Active Directory. Make sure that the Azure Account and Dynamics 365 share the same TenentID (which means the same Microsoft account to login between Azure portal and Dynamics 365 office account).
In order to register the Application in Azure Active Directory, follow the below steps.
After entering the details the registration screen will looks like below
Note: Prior to version Denodo 8, use Virtual Dataport Administration Tool to launch OAuth 2.0 Wizard.
https://login.microsoftonline.com/<azure_directory_id>/oauth2/v2.0/authorize
https://login.microsoftonline.com/<azure_directory_id>/oauth2/v2.0/authorize
Once we have generated Access & refresh tokens for the wrapper, we can create our Custom data source to use the custom wrapper for connecting to our OData 4 data source, In this case: let's assume our Dynamics is running on the following URL:
https://<instance_name>.crm8.dynamics.com/
Note: The crm8 part of the URL can differ depending on the location of the data center.
To create the data source, follow these steps:
https://<instance_name>.crm8.dynamics.com/data/
If in doubt, contact the Dynamics 365 administrator.
Once we have configured our data source pointing to the MS Dynamics 365 server, we can create different views for accessing the desired entities.
As an example, we can create a base view for accessing the following Dynamics url that provides information about Accounts (accounts entity):
https://<instance_name>.crm8.dynamics.com/api/data/v9.0/
To create the base view follow these steps:
Denodo OData4 Custom Wrapper - User Manual
Microsoft Developer Network: Connect to Microsoft Dynamics 365 web services using OAuth
Microsoft Azure Developer’s Guide: Integrating applications with Azure Active Directory