9,280
edits
Integrations: Difference between revisions
Jump to navigation
Jump to search
→Dynamics
| Line 104: | Line 104: | ||
The following applies when using Integrations for connecting to [[Dynamics|Microsoft Dynamics 365]]: | The following applies when using Integrations for connecting to [[Dynamics|Microsoft Dynamics 365]]: | ||
* Use the OData connector. | * Use the OData connector. | ||
* As the URL, use <code><nowiki>https://{organization name} | * As the URL, use <code><nowiki>https://{organization name}.crm4.dynamics.com/api/data/v9.2/</nowiki></code>.<br>You can verify this on your Dynamics server: go to '''Settings > Customizations > Developer Resources''' and look for '''Service Root URL'''. | ||
* If you're using multi-factor authentication, follow the instructions in the connection log: Go to <code><nowiki>https://microsoft.com/devicelogin</nowiki></code> and enter the provided code. | * If you're using multi-factor authentication, follow the instructions in the connection log: Go to <code><nowiki>https://microsoft.com/devicelogin</nowiki></code> and enter the provided code. | ||
* Field mapping - a general guideline: Pay special attention when mapping fields. The system will attempt to suggest a matching field (based on name), however, it's not foolproof. Consider this example of the Primary Contact ID field on the Account entity: rather than the string field use the unique identifier field. | * Field mapping - a general guideline: Pay special attention when mapping fields. The system will attempt to suggest a matching field (based on name), however, it's not foolproof. Consider this example of the Primary Contact ID field on the Account entity: rather than the string field use the unique identifier field. | ||