Do you know that going for a Business Central Dataverse connection setup can be a boon for your business? Do you want to know how? You are reading this blog, which means you use Dynamics Business Central and other applications to support your daily operations.

However, using multiple applications has challenges, like data silos, manual data entry, and inconsistent data. Thus, Dataverse is a single source of truth for sharing data across applications.

Going for Business Central Dataverse connection setup is the first step to ensure seamless integration with other applications. Data from all the applications is stored in Dataverse and synchronized across applications in real time. This allows you to utilize the data for the intended requirements, like creating sales order quotes or maintaining accurate customer records.

In this article, we will explore a step-by-step guide for Business Central Dataverse connection setup and its benefits. 

Let’s understand Microsoft Dataverse first!

What Is Microsoft Dataverse?

Microsoft Dataverse is a cloud-based data storage platform that enables the secure management of business data across applications. Data is organized in tables containing rows (records) and columns (fields) designed for specific data types, such as customer names, invoice amounts, and inventory details.

You may use the default set of pre-defined standard tables, or you can create a customized table for business needs. Its easy integration with Business Central, Power Apps, Power Automate, and Power BI guarantees the integrity of your data across the platform.

Scheduled Sync, Virtual Tables, and APIs: Which One Do You Need? 

Short answer: The standard Dataverse connection copies data between Business Central and Dataverse on a schedule through the job queue. It does not guarantee real-time consistency. If you need live data, use virtual tables or Business Central APIs instead.

MethodHow it worksUse it when
Scheduled synchronizationJob queue entries copy changes between coupled records at set intervals. Data is stored in both systems.Sales and finance both need their own copy of customers, contacts, and products.
Virtual tablesDataverse shows Business Central data without storing it. The data is retrieved at runtime. Needs the Business Central Virtual Entity app from AppSource.You need current Business Central data inside Power Apps or Dataverse and do not want a second copy.
Business Central APIsYour app or flow calls Business Central directly.You are building a custom integration or Power Automate flow and need live reads or writes.

In practice these change expectations. If a salesperson creates an account at 10:02 and finances look for the customer at 10:05, it may not be there yet. Tell your teams that up front, or you will get "the integration is broken" tickets that are not tickets at all.

What are the prerequisites for integration?

Certain prerequisites should be fulfilled before integrating Business Central and Dataverse. These prerequisites ensure a smooth and error-free setup process:

  • Dataverse environment URL: If you own environments, the guide finds them for you. Otherwise, paste the URL of another environment in your tenant.

  • Administrator access on both sides: You need a Business Central Essential or Premium licensed user to run setup. For Dataverse, sign in with an account that has the System Administrator security role and the User Administrator on the tenant. That Dataverse account doesn't need a Business Central license, and you can remove it after setting it up.

  • The environment is not in administration mode: Administration mode makes the connection fail because the integration user has no administrator permissions.

  • Pop-ups allowed for https://login.microsoftonline.com. If the sign-in window never appears, this is usually why.

  • Licensing: Check that your Dynamics 365 and Power Platform plan covers the Dataverse using your plan.

  • Currency, if you work in more than one: You no longer need the two base currencies to match, but you do need at least one exchange rate in Business Central for the currency.

How to Integrate Dynamics Business Central with Dataverse

Setting up the Dataverse Business Central connection can be done in two ways: the Assisted Setup Guide and the Manual Setup.

Using the Assisted Setup Guide: Steps

Microsoft provides an Assisted Setup guide within Business Central that simplifies the process of connecting to Dataverse.

  • Navigate to Business Central > Setup & Extensions > Assisted Setup.

  • Select “Set up a connection to Dataverse.”

  • Provide the Dataverse environment URL.

  • Authenticate using your Microsoft credentials.

  • Choose between user- or team-based ownership for synchronized records.

  • Review and confirm the settings.

  • Verify the settings and click Finish to complete the setup.

Manual Setup via Dataverse Connection Setup Page: Steps

  1. Open Business Central, search for Dataverse Connection Setup, and open the page.

  2. Enter the Dataverse Environment URL.

  3. Provide the necessary authentication details. On-premises setups that don't use a Microsoft Entra account also need the integration username and password.

  4. Set the ownership model and any other options.

  5. Choose Test Connection to confirm the setup work.

  6. Save the settings and enable the connection to start synchronization.

Data Synchronization & Table Mapping

Short answer: Synchronization works on coupled records. A Business Central customer is coupled to a Dataverse account. The integration table mapping says which tables sync and which way. The integration field mapping says which fields move across. Job queue entries then run it on a schedule.

Record Coupling 

Coupling is the link between one Business Central record and one Dataverse row. Without it, nothing syncs for that record. You can couple one record at a time from a card page (a customer card, say), or let a synchronization job create and couple new records for anything uncoupled. Where both systems already hold data, use match-based coupling so you don't create duplicates.

Synchronization Direction

  • One-way: data flows from Business Central to Dataverse, or the other way, but not both. Currencies, for example, only go from Business Central to Dataverse. Salespeople come the other way, from Dataverse users into Business Central.

  • Two-way: changes in either system synchronize. Customers and accounts work like this by default.

  • Incremental: after the first run, only records added or changed since the last successful job are updated.

Standard Table Mappings 

Business CentralDataverseDirectionDefault filter / note
CustomerAccountBoth waysDataverse: Relationship Type is Customer and Status is Active. Business Central: not blocked.
VendorAccountBoth waysDataverse: Relationship Type is Vendor and Status is Active. Business Central: not blocked.
ContactContactBoth waysPerson-type contacts assigned to a company.
CurrencyTransaction CurrencyBusiness Central to DataverseExchange rates come from Business Central.
Salesperson/PurchaserUserDataverse to Business CentralLicensed, active users that aren't integration users.
Unit of MeasureUnit GroupBusiness Central to DataverseCheck your version's Integration Table Mappings page.
ItemProductCheck in your version.Filters vary by version. Confirm in your sandbox.

Note: Treat this as a starting point. Open Integration Table Mappings in Business Central to see what your version does.

Integration Field Mappings and Filters 

Field mappings are where small problems start. Each mapping pairs a Business Central field with a Dataverse column, and you set a direction per field. Custom mapping needs the field to exist on both sides. For filters, use the table filter and integration table filter to limit what syncs, for example, only active customers or only records for the right company when several Business Central companies share one Dataverse environment.

For Canadian businesses with separate companies per province or entity, the company ID that Business Central stamps on synchronized rows matters. Turn on multi-company synchronization on document mappings so one entity's orders don't land in another's books.

Scheduled Jobs and Initial Synchronization 

Business Central ships default job queue entries, and they run in an order that avoids coupling dependencies: currencies, then salespeople, vendors, customers, and contacts. For example, the CURRENCY job checks for exchange rate changes every 30 minutes by default and goes on hold for twelve hours if it finds none. Business Central restarts a held job when something changes on its side. A change made in Dataverse won't wake it up.

Run the initial synchronization in a sandbox first, look at what was created, then repeat in production. It is slower, but cleaning duplicate customers out of a live ledger is much slower.

Common Challenges & Solutions (Troubleshooting) 

Start every investigation in the same place: Integration Table Mappings: select the mapping, then Integration Synch. Job Log. For error details, open Integration Synchronization Errors. Job schedules live under job queue entries.

ProblemLikely causeWhat to do and where
Connection fails.Dataverse environment in Administration mode; sign-in pop-up blocked; account lacks System Administrator role.Turn off administration mode in the Power Platform admin centre. Allow pop-ups from login.microsoftonline.com. Re-run the test connection on the Dataverse connection setup. If the integration solution looks broken, choose Redeploy Integration Solution on the same page.
Records are not syncing.Records are not coupled or filtered out, or the job is on hold due to inactivity.Open job queue entries and check status. Check the mapping's table filters. Remember, a change made in Dataverse won't reactivate a held job; run the sync manually from Integration Table Mappings.
Duplicate recordsFull synchronization runs when both systems already have data; no match-based coupling.Stop the jobs first. Use match-based coupling and couple existing records before syncing again. Clean up in a sandbox before touching production.
Field mapping errorsField missing or different length on one side; mandatory column with no value.Review Integration Field Mapping. Set default values for mandatory fields. Use Default Synchronization Setup to reset a mapping you've broken.
Currency problemsNo exchange rate in Business Central; two-way currency sync attempted.Add a rate on Currency Exchange Rates. Keep currency sync one-way, Business Central to Dataverse. Review the CURRENCY job in the job log.
Sync job keeps failingOne bad record blocked the run; the integration user lost its role.Open Integration Synchronization Errors, fix the record named, then retry. Check the integration user still has the Business Central Dataverse Integration role.
Country codes do not matchDataverse expects ISO-standard codes.Use two-character ISO country codes in both systems.

Note: The most common root cause is two teams changing the same customer into two systems with no agreed owner. Decide which system is the master for each field, then set the mapping direction to match.

Security, Privacy and Canadian Compliance in Practice 

Customer accounts and contacts hold personal information, so the connection is a privacy decision as well as a technical one. For Canadian organizations that usually means PIPEDA, and Quebec's Law 25 where you hold personal information about Quebec residents. Both care about who can see the data and where it lives.

  • The integration runs under an automatically created, non-licensed application user, and only that user should hold the Business Central Dataverse Integration role. Keep human admins out of that role.

  • Remove the one-time Dataverse administrator account after setting up if you do not need it.

  • Check which region your Dataverse environment sits in. Some Ontario and Quebec organizations have contract or policy reasons to care.

  • Sync only what sales need. Fewer fields synced means less personal information copied around.

On the finance side, GST/HST and PST configuration stays in Business Central. The Dataverse connection copies customer and contact data, not tax setup, so confirm tax registration details are kept where your finance team will use them. 

See our guide to Canadian sales tax setup in Business Central.

Why Set It Up? 

Fewer double entries: Sales and finance stop re-keying the same customer, which is where most address and name mismatches come from.

One customer list to argue about, not two: Teams usually notice this first. Savings in time follow only once the workflow is stable.

Better reporting input: With sales and finance data lined up, Power BI dashboards stop needing manual reconciliation.

Access control: Dataverse uses role-based security, which lets you decide who sees synchronized customer data. If you have completed Business Central with Sales integration, this is the layer that makes it manageable.

How Can Dynamics Square Help?

Dynamics Square Canada is a Microsoft Business Central partner in Canada, working with finance and IT teams in Ontario, Toronto, British Columbia and across Canada. We set up the connection in a sandbox first, test coupling and mappings against your real customer data, then move it into production.

We have a team of 150+ consultants that assist you in integration. If you require help developing custom tables, we are here to help you.

Call us at +1 778 381 5388 or write us an email at info@dynamicssquare.ca if you have any trouble regarding integration.

Related reading: Business Central implementation.

Frequently Asked Questions

Open Assisted Setup in Business Central and run "Set up a connection to Microsoft Dataverse." Enter the environment URL, sign in as an administrator, choose Team or Person ownership, test the connection, and enable it. You can also do it manually from the Dataverse Connection Setup page.

Out of the box: customers and vendors with Dataverse accounts, contacts, currencies, salespeople and units of measure, plus products that are mapped. You can change table and field mappings, filters, and direction.

No, the standard connection runs on scheduled job queue entries, and Microsoft says it doesn't guarantee real-time consistency. For live data, use virtual tables or Business Central API.

Dataverse tables show Business Central data without storing a copy. The data is retrieved at runtime. They need the Business Central Virtual Entity app from AppSource.

Check the test connection, the administration mode, and whether the job queue entry is on hold. Then review the Integration Synch. Job Log and Integration Synchronization Errors for the failing record.

Yes, Business Central can connect to a Dataverse environment with a different base currency, as long as currency synchronization runs one way, from Business Central to Dataverse, and exchange rates exist at Business Central.

Shreyansh Gupta - Author
Shreyansh Gupta

Shreyansh Gupta is a Microsoft Dynamics 365 Business Central Solution Specialist with expertise in ERP implementation, solution design, and business process transformation. He specializes in helping organizations translate complex business requirements into scalable Business Central solutions that improve operational efficiency and support long-term growth. His experience spans Business Central configuration, system integrations, data migration, user acceptance testing, and end-to-end ERP project delivery. He brings a structured, business-focused approach to areas including finance, inventory, purchasing, sales, and operational workflows, working closely with stakeholders to align ERP capabilities with real-world business requirements. Shreyansh holds the Microsoft Certified: Dynamics 365 Business Central Functional Consultant Associate (MB-800) certification, along with professional-level finance qualifications.

Revenue Recognition Principle: How It Works in Canada (IFRS 15 and ASPE)

The revenue recognition principle is simple to say: you count revenue when you earn it, not when the money arrives. In practice, it gets awkward fast. A customer pays for a full year upfront. A single contract covers ...

Inventory Reconciliation in Dynamics 365 Business Central

Inventory reconciliation in Business Central is the process of confirming that the value recorded in the inventory subledger, built from item ledger entries and value entries that matches the balance in the general ledger inventory account.

Book a Free Consultation

See How Dynamics Square Can Help Transform Your Business With Microsoft Business Applications.

Phone
contactfor-sede-img