What's New: Business Central Integration with Dataverse (2024 release wave 1)

Overview

The session covers four ways Business Central and Dataverse interact: data sync, virtual tables, data change events and business events. For data sync, it covers linking a Business Central environment to a specific Dataverse environment, adding table mappings to existing integration tables, adding field mappings, a new troubleshooting fact box, and cleanup of sync data when a company or environment is copied. Connection setup pages were also renamed.

The second half covers synthetic relationships between synced tables and virtual tables, and multi-company access to virtual tables. Company can be set globally, per user, or overridden by a custom mapping plugin using the Dataverse shared BC Company ID execution variable. It ends with Power Automate triggers, the new business event subscription pages, and sending events to Application Insights as partner telemetry.

Key points

• Admins can link a Business Central environment to only a specific Dataverse environment.
• New table mappings can be added to existing integration tables, but existing mappings cannot be remapped or duplicated because they are defined in code. New field mappings are inserted as disabled by default.
• Field mappings support most simple data types. Lookup fields and custom logic need developer help.
• Synthetic relationships link synced Dataverse tables to Business Central virtual tables through an assisted setup guide. The virtual table must be enabled, and its API page supplies the fields to pick.
• Virtual table company targeting: a global company setting applies to all users and apps, and a user-specific setting overrides it. A mapping plugin and mapping table can set the Dataverse shared BC Company ID variable per user, app and portal.
• The mapping plugin can be registered with the plugin registration tool at the prevalidation stage. Its example code is to be published after the launch event.
• New business event UI pages show subscriptions, notifications, activity logs and retries. Events are also sent to partner telemetry in Application Insights, set up via the Business Central admin center, with extra custom dimensions.

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 200 “Work Type” at 11:21
• table “Pay Type” at 11:21
• table “Field Service Resource Pay Type” at 11:48
• table “sales shipment virtual table” at 15:29
• table “sales invoice virtual table” at 21:49
• table “mapping table” at 22:10
• other “virtual table API page” at 16:01
• other “BC configuration app” at 27:39
• table “app name company mappings” at 29:14
• table “user table” at 28:19
• page “business event subscription” at 38:21

Not found in BC28-30: table “Pay Type”, table “Field Service Resource Pay Type”, table “sales shipment virtual table”, table “sales invoice virtual table”, table “mapping table”, table “app name company mappings”, table “user table”, page “business event subscription”.

Quotes

• 0:57 “dataverse is a data storage and management layer for business application built on Power Platform that includes Dynamic 365 sales marketing field service and”
• 1:55 “Business Central and those data app can be integrated in such a way that they can enhance each other essentially living up to the”
• 4:16 “admins now have a way of ensuring that that specific business Central uh environment can be linked only with a specific uh data verse”
• 4:57 “we’ve added a capability to add uh table mappings to existing integration tables that has been a recurring request from uh our partners and”
• 6:36 “we do support uh most of the simple data type uh in the mappings but you will still need a developer assistance in case”
• 9:40 “we have actually enabled the use of synthetic relationships uh from business Central”
• 10:20 “you can now actually use the existing apis to sort of supplement uh that data that has been uh that has been synced”
• 13:34 “mappings are by default going to be in u um inserted as disabled”
• 18:27 “we have entered General availability for virtual table in the last release which is uh 23 Wave 2”
• 19:08 “there is no company Concept in data verse so we actually have to support um um um a way for power page uh power”
• 20:08 “we introduced with this release a data verse shared BC Company ID execution variable that will be used by rever virual table plugin to”
• 24:11 “in the mapping table you can create an entry that match your um uh user and apps so in this case um in a”
• 25:11 “this will be published after the uh launch event so you can essentially cut and paste it and modify it right”
• 26:32 “the mapping plugin and M mapping table that uh we built can actually Target different companies”
• 30:47 “business event was uh uh released in public preview for about two releases”
• 31:07 “what’s new in this release in 24 Wave 1 is actually a new UI Pages for troubleshooting minist events”
• 31:47 “Power automate flows that triggered by data cut uh change update uh create update and delete and also business event”
• 33:06 “you can see there are two synthatic relation that relates a native account in data verse with sales credit memo virtual tables”
• 38:01 “there’s a page uh a new page which is called business event subscription here you can see that um I have multiple events that”
• 39:01 “those events are also pushed into partner tary in app Insight uh we have I have set up uh my app insight in this”

Disclaimers in the video

• 25:11 coming-later: code of the mapping plugin will be published after the uh launch event
• 30:47 preview: business event was uh uh released in public preview for about two releases ago 23rd wave 1 release

Presenters (as heard): Sarco, Ivan, Ian, Sandy.