10,730
edits
Important: Deprecating old WebView — Publish failed error
Integrations: Difference between revisions
Jump to navigation
Jump to search
→Dynamics
| Line 105: | Line 105: | ||
* As the URL, use <code><nowiki>https://{organization name}.api.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'''. | * As the URL, use <code><nowiki>https://{organization name}.api.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: | * 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. | ||
: [[File:Primary contact mapping.png|600px]] | : [[File:Primary contact mapping.png|600px]] | ||