How-ToIntegrations

How to Map New Dataverse Fields in Business Central

Learn how to add custom Dataverse table and field mappings for synchronization directly in Business Central without writing code.

Stein Sæstad
7 min read

When you integrate Business Central with Dataverse or Dynamics 365 Sales, the default table mappings cover standard entities like customers, contacts, and items. If you add custom fields or tables in Dataverse, you previously needed a developer to create AL proxy tables and deploy them as an extension before you could include those fields in synchronization.

Starting with 2026 release wave 1 (version 28.0), custom Dataverse tables and fields are available directly in the mapping wizard. Administrators can add new mappings without writing code.

What Changed in Version 28.0

In version 27.0 and earlier:

  • The lookup on the Integration Table column only showed Dataverse tables that were part of out-of-the-box integrations.
  • Adding custom Dataverse tables required a developer to create and deploy them through an AL extension.
  • New or custom fields could not be mapped through the Integration Table Field column.

In version 28.0:

  • New and custom Dataverse tables are available directly from the lookup on the Integration Table column.
  • New and custom fields can be mapped using the Integration Table Field column.
  • The field lookup filters to available fields to reduce errors.

Add a New Table Mapping

  1. Search for Integration Table Mappings using Alt + Q.
  2. Select the New Table Mapping action. This launches the Create new integration mappings assisted setup guide.
  1. In the Table column, select the Business Central table you want to map. The lookup shows all BC tables that are not already mapped.
  2. In the Integration Table column, select the Dataverse table. In version 28.0, this includes custom Dataverse tables.
  3. Set the Integration Table Unique Identifier Field Name to the Dataverse table’s unique identifier column.
  4. Set the Integration Table Modified on Field Name to the field that tracks when records were last modified. Both fields are required for synchronization to work.

Configure Advanced Table Mapping Settings

Select the Advanced action in the wizard to access additional settings:

  • Table Filter: Filter which Business Central records are included in synchronization.
  • Integration Table Filter: Filter which Dataverse rows are synchronized.
  • Table Config. Template Code: A configuration template to prefill missing data when new records come from Dataverse into Business Central.
  • Int. Tbl. Config. Template Code: A template for the reverse direction, prefilling data when records go from BC to Dataverse.

Map Fields

After configuring the table mapping, the wizard asks you to map individual fields.

  1. In the Field Name column, select a Business Central field.
  2. In the Integration Field Name column, select the corresponding Dataverse field.
  3. Set the Direction: choose whether data flows from BC to Dataverse, from Dataverse to BC, or bidirectionally.
  4. If a field should always have the same value, enter it in the Constant column.
  5. Specify whether validations or transformations should be applied during field mapping.

Not all field types can be mapped. The following types are supported: BigInteger, Boolean, Code, Date, DateFormula, DateTime, Decimal, Duration, GUID, Integer, Option, and Text. FlowField and FlowFilter fields cannot be mapped.

Add Fields to an Existing Mapping

You do not need to create a new table mapping to add fields. You can add individual field mappings to an existing table mapping.

  1. On the Integration Table Mappings page, select an existing mapping and choose Fields.
  2. On the Integration Field Mappings list page, select New Field Mapping.
  3. This opens the field mapping step of the wizard. Map the field as described above.

New field mappings are added in a Disabled state. Choose Edit List to enable them when you are ready.

Synchronization Rules and Conflict Resolution

Integration table mappings include rules that control how synchronization jobs handle conflicts.

On the Integration Table Mapping page, the Resolve Deletion Conflicts column lets you choose what happens when a record is deleted in one system:

  • Restore the deleted record.
  • Remove the coupling between the records.
  • Do nothing (resolve manually).

The Resolve Update Conflicts column handles cases where both systems update the same record:

  • Send a data update to Dataverse when sending data.
  • Get a data update from Dataverse when getting data.
  • Do nothing (resolve manually).

After setting a strategy, you can use the Retry All action on the Coupled Data Synchronization Errors page to automatically resolve existing conflicts.

Event-Based Synchronization

By default, event-based synchronization is enabled for table mappings. When a coupled record changes in Business Central, the data is synchronized to Dataverse automatically.

For tables with frequent high-volume changes, automatic synchronization can slow down performance. On the Integration Table Mappings page, you can disable event-based synchronization for specific tables and rely on scheduled synchronization jobs instead.

For background on setting up the Dataverse connection itself, see How to Connect Business Central to Dataverse.

For a broader overview of all new features in this release, see What’s New in Business Central 2026 Release Wave 1.