Microsoft Dynamics 365 CRM
Microsoft Dynamics 365 is a cloud-based business applications platform that provides customer relationship management (CRM). You can land CRM data from Microsoft Dynamics 365 as a data source when landing or replicating data.
For more information about the API, see Web API types and operations.
The following Microsoft Dynamics 365 modules are supported:
-
Sales
-
Marketing
-
Customer Service
-
Field Service
-
Project Service Automation
Only standard objects are supported.
Metadata discovery is dynamic and based on the datasets used in your application.
-
For more information about connecting to SaaS applications, see Connecting to SaaS applications.
-
Depending on your use case, you might need to install Data Movement gateway to move data from SaaS applications. For more information, see When is Data Movement gateway required?.
Supported update methods
For more information, see An overview of target update methods.
Landing tasks:
-
Change data capture (CDC)
-
Reload and compare
Replication tasks:
-
Change data capture (CDC) using Change Tables
-
Full load
Landing data in a data lake tasks:
-
Change data capture (CDC)
-
Reload
When using CDC, you must enable Change Tracking in Microsoft Dynamics 365 for all entities that need to be replicated.
-
Out of the box entities are enabled by default.
-
You can enable custom entities by navigating to the relevant Entity Definition page of your entity and selecting Change Tracking.
For more information, see Enable change tracking for entities.
Preparing for authentication
To access your Microsoft Dynamics 365 CRM data, you need to authenticate the connection with your account credentials.
-
Go to https://portal.azure.com/#blade/Microsoft_AAD_RegisteredApps/ApplicationsListBlade and click New registration.
-
Set Name to Qlik
-
Set the redirect URL to https://connector.qlik.com/auth/oauth/v3.htm.
-
Click Register.
-
Copy the Application ID to Client ID in the connection settings.
-
Go to the API permissions tab, click Add a permission, and select Microsoft Graph.
-
Click Delegated permissions and select Offline_access.
-
Click Add permissions.
-
Click Add a permission.
-
Click Dynamics CRM.
-
Click Permissions, and select user_impersonation.
-
Click Add permissions.
-
Click Grant admin consent for... and thenclick Yes.
-
Click Certificates & secrets.
-
Click New client secret, and select Never or set the expiry as far in the future as possible.
-
Click Add.
Value contains your client secret that you can copy to Client Secret in the connection. You may also want to record the client secret for future use.
Creating the connection
For more information, see Connecting to SaaS applications.
-
Click Authenticate when you have filled in the required connection settings.
You may be asked to log in to the source application.
A window is displayed with an authentication code.
-
Copy the code to the clipboard and return to the connection dialog.
-
Paste the code in Complete authentication with the code provided by the source and click Verify.
Tip noteYou may need to scroll down to see this field.When status is Verified,the authentication is verified.
-
Provide a name for the connection in Connection name.
-
Select Open connection metadata to define metadata for the connection when it has been created.
Setting | Description |
---|---|
Data gateway |
Select a Data Movement gateway if required by your use case. Information note
This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None. For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement. |
Client ID | Client ID. Application ID for the application you created. |
Client Secret | Client secret. You can find your client secret on the application page. on the Certifications and secrets tab. |
Authorization Endpoint | Authorization endpoint. You can find your authorization endpoint on the application page. Click Endpoints, and copy the value in OAuth 2.0 authorization endpoint (v1). |
Token Endpoint | Token endpoint. You can find your token endpoint on the application page. Click Endpoints, and copy the value in OAuth 2.0 token endpoint (v1). |
Service Root URL |
Service root URL. To find the service root URL:
|
Resource |
Resource. Use the first part of your Service Root URL. Example: https://example.crm.dynamics.com |