Skip to content
D365 Reference

UnitOfMeasureConversion

Shared across companies

Unit conversion rules — factor, numerator/denominator, and offsets for converting between two units, referenced by RecId to UnitOfMeasure on both sides; product-specific conversions carry the product's RecId, standard conversions leave it 0

Module: Product InformationNo company partition
Notes

Not in the CDM Tables catalog; structure verified against the Microsoft AX 2012 table reference. Product = 0 (not NULL) marks a standard conversion — a worked example of the no-nulls quirk.

Fields

9 fields

KeyFieldEDTDescriptionTypeLengthFlags
FromUnitOfMeasureRecIdRecId of the unit being converted from — join to UnitOfMeasure to get the symbolint64
ToUnitOfMeasureRecIdRecId of the unit being converted toint64
ProductRecIdRecId of the product this conversion is specific to; 0 (not NULL) means a standard conversion that applies to every productint64
FactorMultiplicative conversion factor from-unit to to-unitreal
NumeratorNumerator of the conversion ratio when expressed as a fractionint
DenominatorDenominator of the conversion ratio when expressed as a fractionint
InnerOffsetOffset applied before the factor (needed for scales like temperature)real
OuterOffsetOffset applied after the factorreal
RoundingHow converted quantities are rounded (nearest, up, or down)enum

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading UnitOfMeasureConversionon Databricks — enums are decoded, 1900-01-01 dates are wrapped to NULL, and the DataAreaId anchor is in place. Set your Unity Catalog location, company, and filter values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : UnitOfMeasureConversion Unit conversion rules — factor, numerator/denominator, and offsets for converting between two units, referenced by RecId to UnitOfMeasure on both sides; product-specific conversions carry the product's RecId, standard conversions leave it 0
-- Purpose: Column-selected read of UnitOfMeasureConversion — auto-generated from field metadata
-- Grain  : One row per recid (surrogate key)
-- Notes  : Auto-generated skeleton for Synapse Link / Fabric Link-landed F&O data (lowercase column names). Enums decoded inline where verified; datetimes stored in UTC; 1900-01-01 dates are sentinels mapped to NULL. System/audit columns omitted — see the quirks guide.
-- ============================================================
SELECT
  u.fromunitofmeasure AS "RecId of the unit being converted from — join to UnitOfMeasure to get the symbol",
  u.tounitofmeasure AS "RecId of the unit being converted to",
  u.product AS "RecId of the product this conversion is specific to; 0 (not NULL) means a standard conversion that applies to every product",
  u.factor AS "Multiplicative conversion factor from-unit to to-unit",
  u.numerator AS "Numerator of the conversion ratio when expressed as a fraction",
  u.denominator AS "Denominator of the conversion ratio when expressed as a fraction",
  u.inneroffset AS "Offset applied before the factor (needed for scales like temperature)",
  u.outeroffset AS "Offset applied after the factor",
  CASE u.rounding WHEN 0 THEN 'Nearest' WHEN 1 THEN 'Up' WHEN 2 THEN 'Down' ELSE CAST(u.rounding AS STRING) END AS "How converted quantities are rounded (nearest, up, or down)"  -- enum: UnitOfMeasureConversionRounding
FROM <catalog>.<schema>.unitofmeasureconversion u
-- Resolve UnitOfMeasure (via FromUnitOfMeasure): uncomment to join on its RecId surrogate key
-- LEFT JOIN <catalog>.<schema>.unitofmeasure fromunitofmeasure ON fromunitofmeasure.recid = u.fromunitofmeasure
-- Resolve UnitOfMeasure (via ToUnitOfMeasure): uncomment to join on its RecId surrogate key
-- LEFT JOIN <catalog>.<schema>.unitofmeasure tounitofmeasure ON tounitofmeasure.recid = u.tounitofmeasure
-- Resolve EcoResProduct (via Product): uncomment to join on its RecId surrogate key
-- LEFT JOIN <catalog>.<schema>.ecoresproduct eco ON eco.recid = u.product
;

2 parameters not filled: <catalog>, <schema>

Relationships

1-hop neighbors — click a table to navigate there. RecId and InventDim edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • UnitOfMeasureConversionUnitOfMeasureRecId ref · N:1
    ON unitofmeasureconversion.fromunitofmeasure = unitofmeasure.recid
  • UnitOfMeasureConversionUnitOfMeasureRecId ref · N:1
    ON unitofmeasureconversion.tounitofmeasure = unitofmeasure.recid
  • UnitOfMeasureConversionEcoResProductRecId ref · N:1
    ON unitofmeasureconversion.product = ecoresproduct.recid

Data Entities That Expose This Table