Small and medium business | Business Central, N...

Online BC & Dataverse integration error: "The specified unit is not valid for this product"

(2) Share

Report

Posted on by CX-09030355-0

I was dealing with the BC - integrated CRM for a customer, specifically the item synchronization issue. It was found that because the customer created the same product in two systems at different times, this product has different unit groups in the two systems. As a result, the BC synchronization function reported an error when inserting the CRM product price level into CRM, just like in the screenshot. We have tried many ways to handle this problem but couldn't solve it. Although the solution of recreating the product can solve this issue, the customer has a large amount of data, so this solution is not accepted. May I ask if there are any other better solutions?

Categories:

Microsoft Dynamics NAV

Dynamics 365 Business Central

I have the same question (0)

All responses (6)

Answers (0)

Sort by

Assisted by AI

Saif Ali Sabri 2,654 Moderator on at

Like (0)

Report
Copy link

Link copied!
This error — “The specified unit is not valid for this product” — occurs when the unit group or unit of measure (UoM) assigned to the product in Business Central does not match the corresponding unit group in Dataverse (CRM). When synchronization runs, Dataverse validates the product’s unit reference, and if the BC item’s unit doesn’t exist or isn’t mapped correctly in CRM, the integration fails.
🔍 Root Cause

The same product was created independently in both systems, resulting in different unit group IDs.

During synchronization, BC tries to insert the product price level using its own unit reference, which Dataverse rejects because the CRM product belongs to a different unit group.

🧩 Recommended Solutions

Align unit groups manually: In Dataverse, open the product record and verify its unit group. Then, in BC, ensure the item’s unit of measure matches the CRM unit group and base unit. If necessary, update the BC item’s UoM to match the CRM product’s base unit.

Use Dataverse Product Mapping table: In BC’s Dataverse Connection Setup, check the Product Mapping table. You can manually link the BC item to the correct CRM product and unit group without recreating the product.

Re-sync with corrected unit references: After aligning units, run Synchronize Products again. BC will update the existing CRM product instead of trying to insert a new one.

Automate unit validation: For large datasets, consider a Power Automate or custom integration script that checks mismatched unit groups before synchronization and corrects them automatically.

💡 Additional Tip
If the customer has thousands of products, avoid recreating them. Instead, export both systems’ product and unit group data, compare via Excel or Power Query, and batch‑update mismatched units using Dataverse API or BC configuration packages.

Was this reply helpful? Yes No
Suggested answer

11manish 842 on at

Like (0)

Report
Copy link

Link copied!
This issue is most likely caused by a Unit Group (Unit Schedule) mismatch between the product in Business Central (BC) and the

corresponding product in Dynamics 365 Sales (CRM).

Because the product was created independently in both systems, each product ended up with a different Unit Group. When BC attempts

to synchronize the Product Price List/Price Level to CRM, CRM validates that the product and unit belong to the same Unit Group. If they

don't match, the synchronization fails.

Before recreating any products:

Identify the Unit Group assigned to the CRM product.

Compare it with the BC Item Unit of Measure setup.

Verify whether the issue is:

A Unit mismatch

A Unit Group mismatch

An incorrect product coupling

Align the units and re-establish the product coupling if necessary.

Re-run synchronization.

In most cases, aligning the Unit Group and correcting the product coupling is the best supported approach and can resolve the

synchronization error without recreating products and losing historical references.

Was this reply helpful? Yes No
Subra 1,247 on at

Like (0)

Report
Copy link

Link copied!

Please move this question from this forum into Business central forum.

Was this reply helpful? Yes No
CX-09030355-0 6 on at

Like (0)

Report
Copy link

Link copied!

Hi Saif Ali Sabri, thank you for your reply, Currently, the UOMs in BC are “G” and “KG”, while the CRM base units are “empty” and “KG”. Do you mean I should create a record in BC where the UOM is “Empty”? BC doesn't allow the UOM to be empty. Please correct me if I've misunderstood.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 17,586 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,
this is a Dataverse limitation more than a BC synchronization issue: Dynamics 365 Sales/Dataverse does not allow changing the Unit Group of an existing Product, so if the same item/product was created separately in BC and CRM with different unit groups, the price list line fails because the unit being inserted is not valid for that product. The standard Microsoft-supported approach is to uncouple the records, make sure Unit Group Mapping is enabled, synchronize Unit Groups / Item UOM / Unit of Measure first, then restart the ITEM-PRODUCT synchronization so BC creates/couples the product with the correct unit group. If the existing CRM product already has transactions and cannot be recreated, then there is no clean standard bulk “fix”; you usually need a controlled migration approach: retire/rename old CRM products, create new corrected products, recouple them, and migrate/update related open price list/items where allowed. I would avoid directly editing Dataverse product unit group data because it can break product/price list consistency.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Assisted by AI

Saif Ali Sabri 2,654 Moderator on at

Like (0)

Report
Copy link

Link copied!
Thank you for your follow‑up and for sharing the screenshots. You’re absolutely right — Business Central does not allow an empty Unit of Measure (UOM). The issue here isn’t about creating an “empty” UOM record, but rather about aligning the base unit and unit group definitions between BC and Dataverse.
🔍 Clarification
In your case:

BC has UOMs G and KG.

Dataverse shows the unit group with KG as the base unit, but the other unit (linked to the product) appears as “empty” because its reference isn’t properly mapped.

This mismatch causes Dataverse to reject the synchronization with the error “The specified unit is not valid for this product.”
🧩 Recommended Fix

Verify the base unit mapping: In Dataverse, open the unit group record (e.g., ITEM AD475 UOM KG) and confirm that the base unit is correctly set to KG. Then, in BC, ensure that the item’s base unit of measure is also KG — not G — if that’s the intended primary unit.

Re‑establish the Dataverse link: In BC’s Dataverse Connection Setup, open the Product Mapping or Unit of Measure Mapping table. Link the BC item’s UOM KG to the Dataverse unit KG explicitly. You don’t need to create an “empty” UOM — just ensure the correct mapping exists.

Re‑sync after mapping correction: Once the mapping is fixed, run Synchronize Products again. BC will update the existing CRM product instead of trying to insert a new one.

💡 Additional Tip
If Dataverse still shows an “empty” unit, it usually means the unit record exists but isn’t linked to the correct unit group. You can open the Dataverse Unit table, locate the orphaned unit, and assign it to the correct unit group manually.

Was this reply helpful? Yes No