Skip to content
D365 Reference

DimensionAttribute

referenceShared across companies

The registry of financial dimensions themselves (cost center, department, business unit…) — one row per dimension, recording which table or view backs its values

Module: FinanceNo company partition

Fields

7 fields · 1 key

KeyFieldEDTDescriptionTypeLengthFlags
KeyNameThe dimension's name (CostCenter, Department, BusinessUnit…) — the natural identifier analysts pivot decoded columns onstring
TypeHow the dimension is backed — a custom value list or an entity-backed dimension; values are not decoded here, use the metadata joinenum
BackingEntityTypeTable ID of the view that supplies this dimension's valuesint
BackingEntityTableNameName of the table or view that backs the dimension's values (e.g. the cost-center view for an entity-backed dimension)string
ViewNameName of the generated database view that exposes this dimension's valuesstring
ReportColumnNameColumn name the dimension surfaces under in financial reportingstring
RecIdRecIdThe 64-bit surrogate key DimensionAttributeValue.DimensionAttribute joins toint64

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading DimensionAttributeon 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  : DimensionAttribute The registry of financial dimensions themselves (cost center, department, business unit…) — one row per dimension, recording which table or view backs its values
-- Purpose: Column-selected read of DimensionAttribute — auto-generated from field metadata
-- Grain  : One row per Name
-- 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
  d.name AS "The dimension's name (CostCenter, Department, BusinessUnit…) — the natural identifier analysts pivot decoded columns on",
  d.type AS "How the dimension is backed — a custom value list or an entity-backed dimension; values are not decoded here, use the metadata join",  -- enum: decode d.type via GlobalOptionsetMetadata join — see quirks guide #enums
  d.backingentitytype AS "Table ID of the view that supplies this dimension's values",
  d.backingentitytablename AS "Name of the table or view that backs the dimension's values (e.g. the cost-center view for an entity-backed dimension)",
  d.viewname AS "Name of the generated database view that exposes this dimension's values",
  d.reportcolumnname AS "Column name the dimension surfaces under in financial reporting",
  d.recid AS "The 64-bit surrogate key DimensionAttributeValue.DimensionAttribute joins to"
FROM <catalog>.<schema>.dimensionattribute d
ORDER BY d.name;

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

  • DimensionAttributeValueDimensionAttributeRecId ref · N:1
    ON dimensionattributevalue.dimensionattribute = dimensionattribute.recid

Data Entities That Expose This Table