Microsoft Dynamics 365 integration

What is Microsoft Dynamics 365?

Microsoft Dynamics 365 Sales is Microsoft’s CRM application for sales teams. It keeps accounts, contacts and opportunities in Microsoft Dataverse; Transportial connects to it through the Dataverse Web API.

What syncs between Microsoft Dynamics 365 and Transportial

• ⇄ Both ways

  Accounts ↔ business relations

  Dynamics 365 accounts and Transportial business relations are kept in sync both ways. Before anything is created, Transportial looks for an existing match by VAT number, then Chamber of Commerce number, then website or e-mail domain, then name — so neither side ends up with duplicates.

• ⇄ Both ways

  Contacts ↔ contact persons

  The contacts of an account are kept in step with the contact persons of the matching business relation.

• ⇄ Both ways

  Opportunities ↔ quotes

  Each quote is an opportunity on the account, and its stage follows the quote status through a stage mapping you can change. Won and lost go through the opportunity close actions of Dynamics 365. Optionally, closing an opportunity as won or lost in Dynamics accepts or declines the quote; this is off by default.

• → To Microsoft Dynamics 365

  Transport orders and invoices → notes

  Transport orders and sent invoices are added as notes on the account, so the sales team sees what a customer ships and is billed for in Dynamics 365.

How to connect Microsoft Dynamics 365

1. In Microsoft Entra ID, register an app for Transportial and create a client secret for it.

2. In the Power Platform admin center, add that app to your Dynamics 365 environment as an application user, with a security role that can read and write accounts, contacts, opportunities and notes.

3. Add the Microsoft Dynamics 365 integration in Transportial with your tenant ID, the client ID and client secret, and the environment URL (for example https://yourcompany.crm4.dynamics.com).

4. Check the defaults: sync direction per object, conflict policy (newest change wins), opportunity stage mapping, field mapping, whether unknown accounts become relations (on) and which relation types are synced.

Sync frequency and limits

• Transportial sends its own changes to Dynamics 365 and checks Dynamics 365 for changes every 15 minutes.
• Sync direction is set per object; when a record changed on both sides, the newest change wins by default.
• Custom columns are mapped to Transportial fields in the field mapping.
• Changes Transportial wrote to Dynamics 365 are never imported again, so updates do not bounce back and forth.

Typical use case

A forwarder’s sales team runs its pipeline in Dynamics 365 Sales, while the operations desk prices and plans in Transportial. A quote sent from Transportial appears as an opportunity on the right account, and when the customer accepts it the opportunity is closed as won. Accounts that sales creates in Dynamics show up as relations, and the orders and invoices that follow are logged on the account.

Frequently asked questions