Microsoft Dynamics 365 | Integration, Dataverse...

Unable to change Sales Unit after product synchronization via Dual Write

(0) Share

Report

Posted on by ML-24081237-0

Hello,

we are currently implementing a Master Data Management (MDM) approach using Dynamics 365 Finance & Operations as the leading system for product master data.

We have identified a limitation when using Dynamics 365 Field Service and Dual Write:

Scenario

Products are created and maintained in Dynamics 365 Finance & Operations.
Products are released to multiple legal entities.
Dual Write synchronizes product data to Dataverse.
Dynamics 365 Field Service uses the product records from Dataverse.

Issue

After a product has been synchronized and used by Field Service, it appears that the Sales Unit of the product can no longer be changed in F&O.

Example:

Base Unit: PCS
Sales Unit should be changed from PCS to M (Meter)

When attempting to change the Sales Unit in F&O, Dual Write fails with the following error:

Request failed with status code BadRequest

CDS error code: 0x80043b16

"The unit is not present in the specified unit schedule."

Entity: msdyn_sharedproductdetails

Weitere Zeilen anzeigen

Our investigation suggests that once the product and its Unit of Measure are established in Dataverse/Field Service, the unit assignment is effectively locked, preventing subsequent changes from F&O.

Business Impact

This behavior creates challenges for Master Data Management:

F&O is intended to be the leading system for product master data.
Unit assignments may need correction or harmonization after product release.
Changes in F&O should ideally be propagated to downstream systems.
Currently, the integration appears to prevent such corrections once Field Service references the product.

Questions

Is this a known product limitation or expected behavior?
Are there any supported procedures for changing Sales Units after synchronization with Field Service?
Is there a recommended MDM design pattern for organizations that need to maintain ownership of Units of Measure in F&O?
Are there plans to improve this behavior in future releases?

Any guidance, best practices, or official Microsoft recommendations would be greatly appreciated.

Thank you.

Categories:

Dynamics 365 general

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Manoj - ManoVerse 1,442 Super User 2026 Season 2 on at

Like (0)

Report
Copy link

Link copied!

Yes, this is expected behavior and a known limitation of the standard Dataverse/Field Service integration. Dataverse products are linked to a Unit Group (Unit Schedule), and the product's unit can only be changed to another unit within the same group.
In your example, changing the Sales Unit from PCS to M (Meter) typically means changing between different unit classes/groups. When Dual Write tries to update msdyn_sharedproductdetails, Dataverse rejects the change and returns:
“The unit is not present in the specified unit schedule”
recommendation would be:
Define the correct unit structure before synchronizing products.
If a cross-unit-class change is required, create a new product with the correct unit and retire the old one.
Use a custom integration design if cross-unit-class changes must be supported.

Was this reply helpful? Yes No
ML-24081237-0 2 on at

Like (0)

Report
Copy link

Link copied!

@Manoj - ManoVerse Thanks for your current answer. That the same knowlege basement my collegue told me today. The point is, we have Field Service, that uses the Dataverse integreation, only for one client of five. So when I export a released product to another client, there are the possibiliy to change the Sales Unit after exporting. Only for the client using Field Service there is no changing allowed.

For MDM it's that point not usefull because we wanna use the same products with same properties at all clients. That means, I can not even create a new poduct, that have the sales unit METER, when there where released products with same name in other clients. There should be only one product with the same name. So for me as leader of MDM it brings me to a not fixual problem, then every product we release in the client with Field Service get the Sales Unit PCS. That not workable for our leading data system Dynamics 365 F&O. Maybe there is possibilty to change the unit once and than it have to be correct.

Was this reply helpful? Yes No