When releasing a product from the Product form to other legal entities, the Dual-Write sync fails with the following error on the EcoResReleasedDistinctProductCDSEntity:
"No default unit set. The product default unit group cannot be defaulted. For integration scenarios (like Dual Write), please make sure that a valid unit ID is mapped to the default unit for this product. The default unit and default unit group columns are mandatory."
Error code: 0x80040265
What's Happening:
The legal entity release flow triggers a write to the products entity in Dataverse via Dual-Write. At the point of sync, Dataverse expects both defaultuomid (Default Unit) and defaultuomscheduleid (Default Unit Group) to be populated. If the unit mapped on the released product in F&O doesn't resolve to a valid Dataverse unit record — whether due to a missing field mapping, an unsynced unit, or a gap in the value map — the write fails.
Note: This issue is specific to the legal entity release flow. Products created manually through Dataverse or synced via other paths may not exhibit the same behavior, pointing to a table map execution ordering issue where the unit reference hasn't landed in Dataverse before the product write is attempted.

Report
All responses (
Answers (