Map new Dataverse fields in Business Central

Microsoft 365 roadmap 573365 · Adapt faster with Power Platform · generally available · roadmap status “Launched”, phase General Availability

What Microsoft says

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. Based on partner and customer feedback, this update removes that dependency. 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. You can refresh the Dataverse field list, add the field to an existing mapping, select the corresponding Business Central field, define the synchronization direction, and enable it for data synchronization. Once enabled, the field participates in sync without modifying extensions or recreating mappings. This enhancement reduces configuration overhead and supports faster adoption of custom Dataverse fields, especially for organizations that frequently customize their Dataverse environments. Business Value: 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.

Dates

• General availability: October CY2026 (2026 release wave 2)
• Public preview: not given
• On the roadmap since 2026-09-30, last changed 2026-09-30

Source: Microsoft 365 roadmap. Status words follow the roadmap.