BC24: Manual integration mapping with Dataverse and Business Central

BC24: Manual integration mapping with Dataverse and Business Central

In the past it wasn’t possible to create manually a simple integration mapping inside Business Central without any coding. You have to create allot of code. See the Microsoft Documentation:
Customizing an Integration with Microsoft Dataverse – Business Central | Microsoft Learn
There is also an extension that you can use:
Sync your BC data to Dataverse with less code – Discover Microsoft Business Central (bertverbeek.nl)

But now this is also possible inside the standard of Business Central:

In that case you don’t have to call al developer but if the fields are already in the Dataverse proxy table you can easily integrate with it.

You can change the integration on two levels. The first is a completely new table and the second is adding fields to an existing table.

Adding fields

When you go to the fields mapping of on existing integration table you can see a new button is there:

When you click on the button you get into a wizard were you can select the fields that you want to integrate with:

You can only integrate the following fields:
BigInteger, Boolean, Code, Date, DateFormula, DateTime, Decimal, Duration, GUID, Integer, Option and Text. Another restriction is on fields that has a relationship and fields that are already mapped.

If you click “Next” and “Finished” it will create the field mapping with the status “Disabled”.

To update existing data, choose Run Unconditional Full Synchronization on the Integration Table Mappings page. The action will synchronize data from the new field mappings you just added.

And if you have done that the field is updated:

New table

When you want a total new table mapping you can use the “New Table Mapping”:

When you opened this option you get also a wizard page that you guide through the process:

And with the advanced button on the second step you can add table filters:

And when you click finished the integration table is created:

So again you don’t need a developer on very simple integration mapping fields!


Anna Brunell

Hi! Will this be in wave 1 2024 or do you know when?

    Bert Verbeek

    Yes this will be in the wave 1 release.

Nicholas Tyndeskov

i have just updated to the newest version of BC for test: 23.5.16502.16589
And these buttons you are talking about is not visible. – Please elaborate what you have activated of features, update or extensions for this to be available.

Thanks. 🙂

    Bert Verbeek

    This option is available in bc24. That is launched on the 1st of April

      Nicholas Tyndeskov

      Thank you, i see the preview for BC24 in new sandbox window.
      I will check it out. 🙂


Wow that makes it a lot easier!

I see flow fields are not available, and maybe a bit unrelated do you know how to synch flow fields from BC to dataverse? I tried following your blog and the microsoft documentation to customize the integration but I can’t get it to work with flow fields. Thanks!

    Bert Verbeek

    You can only sync flow fields one direction. From bc to dataverse.
    You have to do it by code and use calcfielfds before you do the sync.

    But not sure if that is possible in the sync.



Mert Adsay

Hello, i can map datetime fields and when i change any datetime data, it successfully syncs. However, if I change datetime data to null, it does not sync. In integration log it seems unchanged. It is a bug?

    Bert Verbeek

    Then indeed it is a bug. Because in my opinion it would have sync.


Hi Bert,

Thanks the blog.
What would be the cost for using this feature? And would you have to setup the mapping for each company?

    Bert Verbeek

    Hi Sune,
    Sorry I didn’t see this comment. Strange.
    But the costs are mainly on the Dataverse side because you need add some capacity.
    On the Fabric side you can use the cheapest F capacity.
    The mapping is for all de companies.
    But you have to activate it per company the integration in BC.

Leave a Reply

Your email address will not be published. Required fields are marked *

The reCAPTCHA verification period has expired. Please reload the page.