Product masters, released products and the dimension-group residue
How AX 2012's released-product, product-master and product-variant model maps forward to D365 with identity-level fidelity on the surface — and the configuration validation, dimension-group re-testing and costing-version reconciliation that the data upgrade does not perform for you.
What you will be able to do
Explain the AX 2012 released-product and product-master model and confirm its identity mapping to D365
Identify where the data upgrade preserves product records but leaves surrounding configuration unvalidated
Describe product dimension groups, their role in variant generation, and the upgrade implications for configuration technology
Map AX 2012 units of measure, product categories, item attributes and item groups to their D365 equivalents and state the validation required
Trace the product-data load sequence across the canonical wave model and explain why sequencing errors produce foreign-key failures
Introduction
Product data is the one area of an AX 2012 upgrade where the term "identity-mapped" is almost literally true. The shared product (EcoResProduct), the released product (InventTable), product masters, product variants, product dimension groups, item groups, item model groups, units of measure, product categories and product attributes all…
The AX 2012 product model — and its survival into D365
Shared product (EcoResProduct). One record per product per environment. Carries the product number, product name, product type (Item or Service), search name, product subtype (Product or Product master), and the product dimension group assignment.
Product dimension groups and configuration technology
A product dimension group defines which product dimensions are active for a product master. AX 2012 supported four product dimensions:
Item groups, item model groups and posting
Item groups (InventItemGroup) classify released products for inventory posting and reporting. Each released product is assigned to exactly one item group. The item group drives the inventory posting setup — the configuration that maps inventory transaction types (receipt, issue, profit, loss) to main accounts.
Units of measure and conversions
The data upgrade carries all three tables forward. The per-product conversion factors (quantity in alternative UoM = numerator / denominator × quantity in inventory UoM) survive unchanged.
Product categories, hierarchies and attributes
Product categories (EcoResCategory) and category hierarchies (EcoResCategoryHierarchy) are identity-mapped by the data upgrade. The hierarchy types — procurement category hierarchy, sales category hierarchy, commodity code hierarchy — persist with their assignments.
Wave sequencing and the product-data load
In the canonical eight-wave model, product data belongs to Wave 2 — Master data (customers, vendors, products, BOMs). The sequencing dependencies are:
Post-upgrade validation: what to test
The following validation tasks apply after the data upgrade completes — regardless of whether the programme used Mode A (in-place upgrade) or Mode B (reshape with DMF load):
Knowledge check
Summary
Product data is the quietest domain in an AX 2012 upgrade — and that quietness is its own risk. The identity-level mapping of tables, records and key structures creates a false confidence that nothing needs testing.