Error synchronizing items to Dataverse

(7) Share

Report

Posted on by Steve Hohman

Hi,

We are in the midst of a deployment of Business Central, Sales Enterprise, and Field Service. We are a service-based company and will not sell any physical products. We previously had our items in Business Central synchronized with products and services in Sales and Field Service. Due to a limitation of not being able to bill Service-type items in Field Service on a recurring invoice setup, I recreated our very limited set for services we perform as Non-Inventory items in Business Central.

Even when we had the Service-designated items synchronizing, the Unit Groups in Sales were based on the Item number for Business Central. For example, item 1001 replaced the Acreage unit group in Sales with ITEM 1001 UNIT GROUP and then they both had acres below as the unit of measure.

Now that we have retired our nine core services and started with new Non-Inventory items in Business Central, I am getting an error synchronizing the first item and creating a new entry in Dataverse for Sales and Field Service to find.

"CRM Unit Group ITEM 10001 UOM GR does not exist."

As a service company, we have simple needs when it comes to units of measure. Each group will only have one sub measurement - we are not stacking units of measure. Our unit groups and units of measure are:

Acreage
- Acre
Project
- Project
Parcel
- Parcel
Site
- Site
Time
- Hour

While Project, Parcel, and Site may seem to be one in the same, we make distinctions for our clients who would be working their own workflows relating to one of those types.

Here is my question:

What is the correct procedure for setting up Units of Measure (before creating items, I would guess) such that all three platforms can synchronize and match, and the corresponding items and products can also synchronize with Dataverse and therefore between platforms?

I appreciate any insight offered.

Steve

I have the same question (0)

All responses (13)

Answers (1)

Saif Ali Sabri 2,351 Super User 2025 Season 2 on at

Like (3)

Report
To ensure proper synchronization of Units of Measure (UoM) across Business Central (BC), Sales Enterprise, and Field Service via Dataverse, follow these steps:
1. Set Up Unit Groups & Units in Sales (Dataverse First)
Since Sales and Field Service require predefined Unit Groups, start here to avoid auto-generated mismatches.

In Sales Enterprise, navigate to Settings > Product Catalog > Unit Groups.

Create Unit Groups matching your BC structure: Acreage, Project, Parcel, Site, Time.

Within each Unit Group, define a Base Unit (e.g., Acre for Acreage, Hour for Time).

2. Set Up Matching Units of Measure in Business Central

Go to Business Central > Units of Measure and ensure they match the Units in Sales.

Next, go to Unit of Measure Groups (if using BC's Item Unit Grouping) and align them with Sales' Unit Groups.

3. Synchronization Setup in Business Central

Navigate to Setup & Extensions > Assisted Setup > Set Up Dataverse Connection.

Under Product Synchronization Setup, map BC UoM Groups to corresponding Sales Unit Groups manually, if needed.

4. Recreate Your Items in Business Central (Now as Non-Inventory)

Assign items the correct Unit of Measure (UoM) that matches the synchronized UoM in Dataverse.

Ensure item synchronization is enabled via the Product sync in BC.

5. Validate Sync & Resolve Errors

Go to Dataverse Synced Records in Business Central to check any sync issues.

If "CRM Unit Group ITEM 10001 UOM GR does not exist" appears, ensure the Unit Group names match exactly in Sales.

By setting up Units & Unit Groups in Sales first, then aligning them in BC before syncing, you ensure a smooth integration without overrides or missing mappings. 🚀

Was this reply helpful? Yes No
Steve Hohman 68 on at

Like (3)

Report

Saif,

Thank you for the very clear, concise answer. I appreciate it.

Unfortunately, I have followed your steps and am still not able to get this to work without the same unit group errors.

So far I have removed everything from all platforms. Recreated the Units of measure in Sales first, then sent them to Dataverse. I had to disabled the sales and Field Service integrations in BC to reset the Dataverse connection. Once I had those reset and everything enabled again, I started with products in Business Central. Using the synchronized (and verified they are not erroring) Units, I was unable to create new items in the Dataverse.

I have now resorted to trying to make the same products (Non-Inventory) in both BC and Sales at the same time and let them synchronize, but on the Dataverse side, I get the following error:

Default Unit {937AE45D-89EC-EF11-BE21-000D3A3AC7C8} must be coupled to a Dynamics 365 Sales record.

This error repeats for each item I have set up.

Steve

Was this reply helpful? Yes No
Suggested answer

Saif Ali Sabri 2,351 Super User 2025 Season 2 on at

Like (2)

Report
The error "Default Unit {GUID} must be coupled to a Dynamics 365 Sales record" indicates that the Units of Measure (UoM) in Business Central are not properly linked (coupled) with their corresponding records in Sales via Dataverse. The issue is likely due to Business Central not recognizing the existing Units in Dataverse or Sales, causing the sync to fail.
Solution: Manually Couple UoM Records to Fix Synchronization Errors
1. Verify & Retrieve Unit Groups and Units in Sales
Since you've already set up Units in Sales first:

Go to Sales Enterprise > Product Catalog > Unit Groups and confirm that all Units and Groups exist correctly.

Open Advanced Find (or Dataverse Table Explorer) > Unit and Unit Group Tables to retrieve the exact GUIDs of the existing units.

2. Manually Couple Business Central UoMs to Dataverse

In Business Central, navigate to Dataverse Synced Records under Integration Table Mappings.

Look for the Unit of Measure table and check if it has records listed. If missing, manually add mappings:

Open the BC Unit of Measure list (Units of Measure page).

For each UoM, select Process > Coupling > Link to Dataverse Record.

Choose the corresponding unit from Dataverse/Sales.

3. Check Default Unit Mapping in Sales

In Sales, each Product must have a Default Unit assigned. If the product exists without a correctly mapped default unit, this will cause sync issues.

Go to Products > Open a Product Record > Ensure Default Unit is Set and Active.

If not linked, manually assign a default unit in Sales, then retry the sync.

4. Restart Synchronization from Business Central

In BC, go to Dataverse Connection Setup > Synchronization Rules for Products.

Ensure that Units of Measure and Products are enabled for sync.

Run Full Sync again and check for errors.

Expected Outcome
After manually coupling Units between BC and Sales, the synchronization should process correctly, and the error "Default Unit {GUID} must be coupled to a Dynamics 365 Sales record" should no longer appear.
Let me know if you run into any additional sync issues! 🚀

Was this reply helpful? Yes No
Steve Hohman 68 on at

Like (2)

Report
Saif,

I am going through the steps you sent, but am running into a road block in step 2.

2. Manually Couple Business Central UoMs to Dataverse

In Business Central, navigate to Dataverse Synced Records under Integration Table Mappings.

Look for the Unit of Measure table and check if it has records listed. If missing, manually add mappings:

Open the BC Unit of Measure list (Units of Measure page).

For each UoM, select Process > Coupling > Link to Dataverse Record.

Choose the corresponding unit from Dataverse/Sales.

When I navigate to Integration Table Mappings, I cannot find anything that says "Dataverse Synced Records". Is this maybe caused by the fact that I am using Dynamics Business Central Essentials and not Premium?

I have looked in each menu and added a screenshot so you can help me find this.

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 20,275 Super User 2025 Season 2 on at

Like (2)

Report

if this helps: https://learn.microsoft.com/en-us/dynamics365/business-central/admin-troubleshoot-sales-synchronization

Was this reply helpful? Yes No
Suggested answer

Saif Ali Sabri 2,351 Super User 2025 Season 2 on at

Like (1)

Report
You're in the right place, but "Dataverse Synced Records" is not explicitly labeled in Business Central. Instead, you need to manually couple Units of Measure from the Units of Measure page.
Since you're using Business Central Essentials, that shouldn't be a blocker. Let's go through the correct steps:

Manually Couple Units of Measure in Business Central

Go to the Units of Measure List

In Business Central, search for "Units of Measure" and open the page.

Check for Existing Couplings

In the Units of Measure list, look for the Coupled to Dataverse column (if available).

If missing, select a UoM and go to More options > Related > Dataverse > Coupling.

Manually Link a UoM to a Dataverse Record

Select a UoM (e.g., "Acre").

Click Process > Coupling > Link to Dataverse Record.

Search for and select the corresponding Sales Unit of Measure (Dataverse record).

Save the changes.

Repeat for All UoMs

Ensure all UoMs in Business Central are linked to existing UoMs in Dataverse.

Run Full Synchronization

Navigate to Integration Table Mappings (as shown in your screenshot).

Select ITEM UOM (or UNIT GROUP, if applicable).

Click Run Full Synchronization under the "More options" menu.

Why This Fixes the Error
The error "Default Unit {GUID} must be coupled" means Business Central is trying to sync a product that references a Unit of Measure that does not exist or is not linked in Dataverse. Manually coupling the UoMs ensures BC recognizes the correct Units already in Dataverse, preventing sync failures.

Next Steps if the Error Persists

Check the Unit Groups in Dataverse: If BC tries to create a unit group with an unexpected name, correct the naming in Sales first.

Verify Product Sync Setup in BC: Make sure the synchronization rules are correctly mapped for items and units.

Check the Integration Job Log: Look for details under Integration Synch. Job Log (shown in your screenshot).

Try these steps and let me know if you're still hitting roadblocks! 🚀

Was this reply helpful? Yes No
Steve Hohman 68 on at

Like (2)

Report

Saif,

I certainly appreciate your responses, but I am just not seeing the dataverse coupling settings. I also verified that I do not see the setting you are guiding me toward in our Sandbox environment.

Here is what I see in the Units of Measure list:

The closest I get is when I open this table in Analysis mode, I can add the Coupled to Dynamics 365 Sales column there and it is indeed set to "No", but from Analysis mode, I am not able to edit the coupling.

Steve

Was this reply helpful? Yes No
Suggested answer

Jainam M. Kothari 15,631 Super User 2025 Season 2 on at

Like (2)

Report

May this can help : https://stackoverflow.com/questions/73338130/synchronization-issue-with-customizing-an-integration-with-microsoft-dataverse

https://learn.microsoft.com/en-us/dynamics365/business-central/admin-synchronizing-business-central-and-sales

Was this reply helpful? Yes No
Gerardo Rentería Ga... 25,213 Most Valuable Professional on at

Like (2)

Report

Hi, good day
I hope this can help you, and give you some hints.

Synchronize Multiple Units of Measure from D365 BC to D365 Sales

Solved: Unit of Measure Within a Unit of Measure

Best Regards
Gerardo

Was this reply helpful? Yes No
Suggested answer

Saif Ali Sabri 2,351 Super User 2025 Season 2 on at

Like (1)

Report
Thanks for the additional screenshots! It’s clear that the Coupling option for Units of Measure is missing from your Business Central environment, which explains why you can’t manually link them.
This usually happens due to one of these reasons:

Dataverse integration for Units of Measure is not fully enabled in Business Central.

The integration table mapping for Units of Measure (ITEM UOM) is missing or not enabled.

Your Business Central license or environment doesn’t support manual coupling for Units of Measure (unlikely, but possible in certain editions).

Let’s troubleshoot and enable manual coupling
Step 1: Check Integration Table Mapping for ITEM UOM

Go to: Integration Table Mappings (search for "Integration Table Mappings" in BC).

Find "ITEM UOM" (Item Unit of Measure) in the list.

In your previous screenshot, this row exists but check if the Synchronization Enabled box is checked.

If Synchronization is not enabled, select the row and enable it.

Step 2: Enable the Coupling Option for UoMs
If the ITEM UOM mapping exists and sync is enabled, but coupling is still not available:

Go to Business Central Admin Center (admin.powerplatform.microsoft.com).

Navigate to Environments > Select Your Environment.

Under Features, look for any settings related to Dataverse coupling or synchronization.

If you see an option to enable sync for Units of Measure, turn it on.

Step 3: Force a Resync of UoMs with Dataverse
If coupling is still missing:

Go back to Integration Table Mappings in BC.

Select ITEM UOM and click Run Full Synchronization.

Wait for the sync to complete, then check the Units of Measure list again to see if coupling appears.

Step 4: (If Still No Coupling) Manually Reset the Integration Mapping
If none of the above works, try resetting the integration for UoMs:

In Integration Table Mappings, select ITEM UOM and click Delete Couplings.

Then, click Run Full Synchronization again.

Check if the Coupled to Dynamics 365 Sales column updates or becomes editable.

Expected Outcome
After these steps, you should either:
✅ See the Coupling option in Units of Measure, allowing you to manually link them.
✅ Have Business Central automatically sync the Units correctly from Dataverse.

Final Alternative if Nothing Works
If the coupling feature is still not available, your BC environment might not support manual UoM coupling due to a limitation in Business Central Essentials. In that case:

Manually create the same Units in both Business Central and Sales with identical names.

Let BC auto-create and sync UoMs (instead of manually linking them).

If the sync still fails, check the Integration Job Log (search for "Integration Synch. Job Log" in BC) for more details.

Try these steps and let me know if anything changes! 🚀

Was this reply helpful? Yes No