Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
| Enabled for | Public preview | General availability |
|---|---|---|
| Users, automatically | 
Apr 5, 2024 |
- |
Business value
Business needs change, and so do business processes. When business processes change, you need to quickly and cost-effectively update integrations that exchange data with Business Central.
Feature details
You can add new table mappings by selecting New Table Mapping on the Integration Table Mappings page.
This action starts the New Integration Mappings guided setup, which helps you set up new integration table and field mappings.
When you enter an Integration Table Mapping Name, select Next to set up new table mapping details.
In this step, specify a Table in Business Central and an existing Integration Table in Dataverse that you want to map. Enter the Dataverse table's unique identifier in Integration Table Unique Identifier Field Name and the Integration Table Modified on Field Name. You need these fields for data synchronization to work.
Note
The lookup on the Table column shows all Business Central tables, including custom tables, that you didn't map yet. It excludes those tables that exist on your Integration Table Mappings page. The lookup on the Integration Table column shows only Dataverse tables (AL Proxy Tables) that are part of out-of-the-box integrations. To add extra or custom Dataverse tables, work with a developer to create and deploy them through an extension.
The Advanced action opens extra table mapping settings that you can set up.
In the Advanced section, use the Table Filter field to specify filters for Business Central. Use the Integration Table Filter field for Dataverse data to include in data synchronization. To prefill missing data when new data comes from either application, use the configuration template codes in Table Config. Template Code and Int. Tbl. Config. Code.
Select Next to specify the field for the new mapping.
In this step of the guide, you match a Business Central field in the Field Name column with a Dataverse field name in the Integration Field Name column. You can also specify a Direction value, set the field to always contain the same value in the Constant column, and indicate whether validations or transformations need to be applied during field mapping.
Note
To reduce errors, the Integration Table Field column's lookup filters to a list of available fields. You need help from a developer to map fields that the filters don't include:
- Enabled fields.
- FlowField and FlowFilter fields. You can't use the guide to map these fields.
- Fields of the following types: BigInteger, Boolean, Code, Date, DateFormula, DateTime, Decimal, Duration, GUID, Integer, Option, and Text. You can only map these field types.
Select Next to go to the last step of the guide. This step shows what happens based on your input.
Select Finish to create your new integration table mapping with the field mappings you defined. This selection also creates a Synchronization Job Queue Entry to synchronize data.
You can add new field mappings to existing integration table mappings through the Integration Field Mappings List page. To open this page, select Fields on the Integration Table Mappings page.
Select New Field Mapping to open the field mapping step of the New Integration Mapping assisted setup guide. Then, follow the preceding steps.
Note
When you add new field mappings to an existing table mapping, the new field mappings are disabled. Select Edit List to enable them.
Geographic areas
Visit the Explore Feature Geography report for Microsoft Azure areas where this feature is planned or available.
Language availability
Visit the Explore Feature Language report for information on this feature's availability.
Tell us what you think
Help us improve Dynamics 365 Business Central by discussing ideas, providing suggestions, and giving feedback. Use the forum at https://aka.ms/bcideas.