9,270
edits
Join the Power Platform Masterclass #2 starting April 23
Integrations: Difference between revisions
Jump to navigation
Jump to search
→Use cases
| Line 90: | Line 90: | ||
;Export Entity / Import Entity: Alternatively, you can export/import mapping for a single entity. | ;Export Entity / Import Entity: Alternatively, you can export/import mapping for a single entity. | ||
== Use cases == | |||
Some integrations have certain prerequisites and require additional configuration to work. | |||
=== Business Central === | |||
The integration with Microsoft Dynamics 365 Business Central is described in a [[Business_Central#Register_Resco_application_in_Business_Central|separate article]]. | |||
=== Dynamics === | |||
The following applies when using Integrations for connecting to Microsoft Dynamics 365: | |||
* Use the OData connector. | |||
* 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. | |||
* 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: | |||
: [[File:Primary contact mapping.png|600px]] | |||
== Technical information == | == Technical information == | ||