Business Central Dataverse integration that keeps records in agreement
A Business Central Dataverse integration syncs customers, contacts, items, currencies and more between your ERP and Microsoft Dataverse. It is the data platform behind Dynamics 365 Sales and the Power Platform. We set up the connection and decide which side owns each record. Then we configure the mappings and watch the sync jobs, so sales and finance see the same information.
Last updated
What a Business Central Dataverse integration gives you
Dataverse stores the business data used by Dynamics 365 Sales, Customer Service, Field Service and apps built on the Power Platform. Business Central ships with a standard integration to it. Once you connect, a customer in the ERP and an account in Dataverse become one coupled pair. Changes to either can flow to the other.
The practical benefit is one version of the facts. A salesperson in Dynamics 365 Sales sees the same customer details that finance maintains. They also see item and price information from the ERP. Orders won in Sales can become sales orders in Business Central without retyping. Posted invoices can show up back in Sales.
Talk through your data flow →
- ✓Customers and accounts
- ✓Contacts at those customers
- ✓Items and products
- ✓Currencies and units
- ✓Salespeople and users
Setting up a Business Central Dataverse integration connection
Business Central has an assisted setup guide for connecting to Dataverse. It asks for the environment address and an admin sign-in. Then it installs an integration solution in Dataverse. It also creates an integration user, and the sync runs under that user. A company in Business Central links to a business unit on the Dataverse side.
Before we run the guide, we prepare both sides. That means the right security roles in Dataverse and matching currencies. We also decide which Business Central company connects. If you use Dynamics 365 Sales, a further setup turns on the sales tables such as opportunities, quotes and orders. We try everything first between a sandbox and a test environment.
Prepare the connection together →- ✓Dataverse environment chosen
- ✓Administrator accounts available
- ✓Base currencies aligned
- ✓Company to business unit decided
- ✓Sandbox pair for testing
Table mappings in a Business Central Dataverse integration
Integration table mappings drive the integration. Each one pairs a Business Central table with a Dataverse table and lists the fields that correspond. It also states a direction: to Dataverse, from Dataverse or both ways. Filters on a mapping limit which records take part, which keeps test or blocked records out.
You must couple existing records before they sync. Match-based coupling pairs them on a field, such as the name. Records with no match can be created on the other side. We decide ownership field by field. Two-way sync of everything tends to end with each side overwriting the other.
Decide record ownership →- ✓Direction per table
- ✓Owner per field
- ✓Filters on each mapping
- ✓Match rules for coupling
- ✓Records with no match handled
Sync jobs and monitoring for Business Central Dataverse integration
Sync runs through job queue entries, one for each mapping, on a schedule you can adjust. A sync log records every run. An errors page lists the records that fail, with the reason. The usual causes are a missing field, a duplicate, or a related record that is not coupled yet.
Left alone, errors pile up. Then trust in the data fades. So we set up a routine. A named person checks the error list. They fix the source data and retry. We also tune schedules so busy tables sync often and static ones rarely. After each Business Central update, we check job queue health.
Set up sync monitoring →- ✓Synchronization log checked
- ✓Failed records corrected at source
- ✓Schedules tuned per table
- ✓Job queue entries healthy
- ✓Named owner for errors
Virtual tables and delivery of a Business Central Dataverse integration
Not everything needs copying. Business Central can show its data to Dataverse as virtual tables. These read live from the ERP and store no duplicate. That suits Power Apps and Power Pages that need current data. For custom tables or extra fields, a developer extends the integration with AL code and new mappings.
We deliver the work in order. First come ownership rules and a sandbox connection. Next we couple existing records and run a trial with real users. Production comes last. The main pitfalls are duplicate accounts from careless coupling and mismatched currencies or units. You receive the mapping document, the coupling results and a guide to the monitoring routine.
Request an integration plan →- ✓Ownership rules per table
- ✓Mapping and filter document
- ✓Coupling results report
- ✓Tested sandbox connection
- ✓Monitoring guide for staff
Business Central Dataverse integration questions
What is Dataverse, in plain terms?
Dataverse is Microsoft's cloud data platform. It stores the tables used by Dynamics 365 apps such as Sales and Customer Service. It also serves apps built with the Power Platform. When you connect Business Central to it, those apps can share customers, items and related records with the ERP. So everyone works from the same data.
Is the Dataverse connection part of standard Business Central?
Yes. Business Central includes the integration, its assisted setup and the standard table mappings. You do need a Dataverse environment and the right licenses on that side. An example is Dynamics 365 Sales, if your sales team will work there. We check the license side with you before we start the Business Central Dataverse integration.
Do we need Dynamics 365 Sales to use it?
No. You can connect Business Central to a Dataverse environment that holds only Power Platform apps. Dynamics 365 Sales adds sales tables such as opportunities and quotes. Business Central has further setup for that case. We tell you which path fits after we hear how your sales team works today.
Does data synchronize instantly?
Not instantly. Job queue entries schedule the sync, so changes arrive after the next run. A user can also sync a single record on demand from its page. Virtual tables work differently, because they always read live data. We choose the schedule for each table, so busy data stays fresh and static data does not add load.
Can custom fields and tables be included?
Yes, with development. A custom table or field needs a matching column in Dataverse. It also needs an AL extension that adds the integration table and mapping. We build and test these in a sandbox pair before we turn them on in production. That way, your live data stays safe while we test.
Book a discovery call
Let's talk through your move to Business Central.
A focused call with a senior consultant. We learn how your business runs today, give you an honest view on whether Business Central fits, and outline scope and next steps before you commit to anything.
What happens after you send the form