What's New: Dataverse & Dynamics 365 App Integration (2023 release wave 2) Part 1

Overview

This is part 1 of the 2023 release wave 2 session on Dataverse and Dynamics 365 app integration. It covers how multiple companies from multiple Business Central environments can access data in the same Dataverse environment, including company filter handling, stricter document filtering, and multi-tenant Azure AD support. It also recommends consolidating data in one master data company before integrating.

The session then covers multi-currency synchronization, additional field mappings, turning off event-based synchronization per mapping, virtual table visibility during assisted setup, and removed commercial blockers for integrating Dynamics 365 apps. A demo shows multi-company setup, base currency conversion, virtual tables, and the default environment and company selection.

Key points

• Multiple companies from multiple Business Central environments can access data in the same Dataverse environment. Turning on multi-company sync removes company filters on user- and team-owned tables such as accounts and contacts. Sales quote and order sync becomes stricter: users must pick the Business Central company that will process each document. Organization-owned tables such as currency are not affected.
• Recommended approach: consolidate data in one master data company in Business Central, synchronize between companies with master data management, then integrate with central Dataverse or Dynamics 365 Sales. This improves performance and avoids service protection limits.
• Multi-currency: Business Central local currencies are added to Dataverse automatically and amounts are converted on the fly. The Dataverse base currency must be set up as a regular currency in Business Central with exchange rates.
• Customer, vendor, contact, salesperson and opportunity mappings have additional fields. They are disabled by default, and users can enable them without a developer.
• Event-based synchronization can be turned off per integration table mapping to reduce errors and sync events. Default settings are unchanged to avoid disrupting existing integrations.
• In assisted setup for Dataverse, specific virtual tables can be made visible, one at a time or in bulk. More can be added later from the connection setup page.
• Each user can set and change a default Business Central environment and company for opening coupled records from Dynamics 365 Sales. The system also recommends coupling criteria for simple tables such as payment terms and currencies.

Features

AL objects mentioned

As heard in the captions. A name that matches one object page by exact type and name links to it; the others stay as named.

• table “account” at 1:39
• table 5050 “Contact” at 1:39
• table “sales quotes” at 1:39
• table 4 “Currency” at 2:19
• table 3 “Payment Terms” at 10:26
• table 18 “Customer” at 10:46
• table 23 “Vendor” at 10:46
• page “integration field mapping” at 6:52
• page “integration table mappings” at 14:03
• page 118 “General Ledger Setup” at 13:51
• table “sales shipment” at 12:58
• table 111 “Sales Shipment Line” at 12:58

Not found in BC28-30: table “account”, table “sales quotes”, page “integration field mapping”, page “integration table mappings”, table “sales shipment”.

Quotes

• 1:18 “2023 release wave two you can now unlock scenarios where multiple companies from multiple business central environments must access data in the same”
• 1:39 “company filters get removed on user and team own tables such as account or cont contact tables sales quotes order”
• 5:08 “integration now ensures seamless synchronization when multiple currencies are involved”
• 5:28 “the only prerequisite that you uh that you have is having data ver based currency set up as a regular currency in business Central”
• 6:31 “customer vendor contact salesperson and opportunity integration field mappings now have additional Fields available for you to map”
• 7:32 “the default settings for the event-based synchronization stay unchanged to avoid disrupting uh existing”
• 8:50 “the commercial blockers for integrating various Dynamic 365 apps have been removed earlier this year”
• 10:26 “for some simple tables like payment terms or currencies we can automatically recommend coupling criteria”
• 18:08 “in the demo you saw uh how integration Works in multic company and multi- environment setting conversion of Base uh transaction currency making virtual”

Disclaimers in the video

• 0:38 other: some improvements have been introduced in July as part of the minor updates for 2023 release Wave 1
• 7:32 other: The default settings for the event-based synchronization stay unchanged to avoid disrupting uh existing Integrations

Presenters (as heard): Ian ktic, Sandy.