Hi, Readers.
Dynamics 365 Business Central 2026 wave 1 (BC28) is generally available. More details: General Available: Dynamics 365 Business Central 2026 release wave 1 (BC28)
I will continue to test and share some new features that I hope will be helpful. In this post, I would like to talk about Map new Dataverse fields in Business Central.
Map new Dataverse fields in Business Central
As an administrator, you can map newly added Dataverse fields without recreating table extensions or writing code, reducing configuration effort and supporting faster adoption of custom fields and solutions. This improvement makes it easier to keep Business Central and Dataverse aligned as Dataverse schemas change.
https://learn.microsoft.com/en-us/dynamics365/release-plan/2026wave1/smb/dynamics365-business-central/map-new-dataverse-fields-business-central?wt.mc_id=DX-MVP-5004336
For the Dataverse Connection Setup, I’ll briefly bring it up this time, check out the post below for more details if you need to.
Dynamics 365 Sales and Business Central integration setup (Set up a connection to Dataverse and Set up a connection to Dynamics 365 Sales)
Note:
These tasks require the System Administrator security role in Dataverse and Business Central.
Working on it…
Done.
This feature simplifies how administrators keep Business Central and Dataverse aligned as Dataverse schemas evolve. Previously, exposing new or existing custom Dataverse fields required creating or updating a table extension (PTE) in the integration layer. More details: Business Central 2024 wave 1 (BC24): Add table and field mappings to existing integration tables (Dataverse)
When a new field is added in Dataverse—such as a custom field in Dynamics 365 Sales—you can now map the field directly from the Integration Table Mappings page.
Let’s look at a simple example. In the default settings, BC Customer table integrates the Dataverse Account table.
You can find the Account table in Dataverse, choose Edit.
Choose New column to add a new field.
As a test, I added a new field, VAT Registration No.
Then return to the Integration Table Mappings page in Business Central.
Choose Fields.
Choose New Field Mapping.
The Field Name on the left represents all the table fields in Business Central, while the Integration Field Name on the right represents the table fields in Dataverse.
With this wave (BC28), no code is required, the newly added field in Dataverse is already visible and can be mapped.
Done.
The default status is Disabled.
You can choose Edit List and then enable it manually.
Great.
This enhancement reduces configuration overhead and supports faster adoption of custom Dataverse fields, especially for organizations that frequently customize their Dataverse environments.
Great, give it a try!!!😁
PS:
1. Although it wasn’t specified in the Release Plan, what is the status of the new table? I did the following test.
First, I created a new table in Dataverse.
Done.
Then grant the permissions for this table to the Application User used for integration.
Roles in a managed solution cannot be edited
Unfortunately, this newly created table cannot be found directly on the Create New Integration Mappings page. For new tables, we still need to use the previous method. More details: Dynamics 365 Business Central: Customizing an Integration with Microsoft Dataverse (Integrate custom tables)
2. Dynamics 365 Business Central Blog Series: Integrate with Microsoft Dataverse
END
Hope this will help.
Thanks for reading.
ZHU
コメント