I am submitting this idea on behalf of customers and partners who have encountered a recurring limitation in Dynamics 365 Supply Chain Management during go‑live or data migration scenarios.

In these cases, an item is created with an incorrect Inventory Unit of Measure, and the opening inventory balance is subsequently posted using that incorrect unit. Once this opening transaction is posted, the system no longer allows the Inventory Unit of Measure to be changed, as inventory transactions already exist. While this behavior is understood and aligns with current product design principles, it creates a significant challenge when the issue is identified immediately after go‑live and before operational usage begins.

For many customers, especially those operating in integrated supply chains, the item number must remain unchanged because it is shared across manufacturers, customers, and multiple external systems. As a result, standard alternatives such as recreating the item or using a different item number are often not viable, as they would introduce disruption to integrations and daily operations.

From a business perspective, the Inventory Unit of Measure is fundamental, as it is used for base on‑hand calculations and inventory valuation. When the unit is incorrect at go‑live, customers are left with inaccurate opening inventory and limited supported options to remediate the situation.

Customers and partners are therefore requesting a supported, controlled correction mechanism for early‑stage scenarios (such as go‑live or migration), where the issue is limited to opening inventory. Providing such a capability would help customers resolve migration‑related data issues while preserving data integrity, auditability, and alignment with Microsoft‑supported practices.