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?
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?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
4
Share
Report
All responses (
Answers (
