Microsoft Dynamics CRM
The Qlik Microsoft Dynamics CRM Connector lets you run FetchXML queries to fetch Microsoft Dynamics CRM data and load it directly into your Qlik Sense app.
The connector can fetch data from the following Microsoft installations and services:
- Dynamics CRM 365 (online)
- Dynamics CRM 365 (on-premises)
- Dynamics CRM Online
- Dynamics CRM 2016
Ways to access your data
To access your
AuthType=Office365; Url=https://contoso.crm.dynamics.com; Usernameemail@example.com; Password=passcode;
The connection string parameters are described here:
Loading data from tables
After you authenticate the connector with a valid connection string, you can use the following table to select and load data. To run this table, you need to enter an XML query.
|FetchXML||Use this table to run an FetchXML query that selects data from your Microsoft Dynamics CRM account and creates a data load script.|
For reference on how to construct a FetchXML query, see the FetchXML documentation.
To select and load data from a table, enter the required table parameters and click Preview data. Required parameters are marked with an asterisk (*). The table fields are displayed under the Data preview tab. You can select fields individually by selecting the box beside each field name. Select Insert script after you have made your selection.
Working with the Microsoft Dynamics CRM API quota limits
Reference - Microsoft Dynamics CRM developer documentation
You can refer to the Microsoft Dynamics API documentation to learn more about the requirements and restriction imposed by the Web API.
You have exceeded the API limits that are imposed on the Qlik Web Connectors by the Microsoft Dynamics CRM
To reduce the impact of reaching the API rate limits, develop your app with the following in mind:
- Extract only the data you need.
- Reload one Microsoft Dynamics CRM-based application at a time.
- Ensure that loops in your script that make API calls will not result in infinite loops.
Some fields are missing after connecting to a new environment
The connector is pointing to the wrong MS Dynamics CRM environment and may be trying to use the old instance.
Add the following attribute to the connection string in your load script.