D365 Reference

DimensionAttributeValue

mainShared across companies

One row per used value of a financial dimension — the middle hop that ties a value-set item back to the dimension it belongs to and the backing record that defines it

Module: FinanceNo company partition

What the badges mean

main: Table group: how F&O categorizes the table's role — main entity, group/header, transaction, worksheet header, worksheet line, reference, parameter, or framework.
Shared across companies: The table carries no DataAreaId— rows aren’t partitioned per company, so a query never needs (and can’t use) a company filter here (see the quirks guide).
Date-effective: The table carries a ValidFrom/ValidTo effectivity window — a join without a date filter multiplies every key by its history (see the quirks guide).

Fields

9 fields

9 fields.

Table fields: key flag, field name, extended data type, description, data type, length, and quirk flags. 9 fields.
Field	EDT	Description	Type	Flags
DimensionAttribute	RecId	RecId of the dimension in DimensionAttribute this value belongs to — the hop that tells you whether a value is a cost center or a department	int64	RecId
EntityInstance		RecId of the backing record (in the dimension's backing view) that defines this value	int64
DisplayValue		The dimension value code as displayed (e.g. the cost-center code)	string
IsSuspended		Whether the value is suspended and blocked from new postings	enum	Enum
IsDeleted		Soft-delete flag — filter deleted values out of dimension lookups	enum	Enum
ActiveFrom		Date the value becomes valid for posting	date
ActiveTo		Date the value stops being valid for posting	date
BackingRecordDataAreaId		Company of the backing record, populated for company-specific dimension values	string
RecId	RecId	The 64-bit surrogate key DimensionAttributeValueSetItem.DimensionAttributeValue joins to	int64	RecId

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading DimensionAttributeValue on 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

CatalogSchema

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

-- ============================================================
-- Table  : DimensionAttributeValue One row per used value of a financial dimension — the middle hop that ties a value-set item back to the dimension it belongs to and the backing record that defines it
-- Purpose: Column-selected read of DimensionAttributeValue — 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
  d.dimensionattribute AS "RecId of the dimension in DimensionAttribute this value belongs to — the hop that tells you whether a value is a cost center or a department",
  d.entityinstance AS "RecId of the backing record (in the dimension's backing view) that defines this value",
  d.displayvalue AS "The dimension value code as displayed (e.g. the cost-center code)",
  d.issuspended AS "Whether the value is suspended and blocked from new postings",  -- enum: decode d.issuspended via GlobalOptionsetMetadata join — see quirks guide #enums
  d.isdeleted AS "Soft-delete flag — filter deleted values out of dimension lookups",  -- enum: decode d.isdeleted via GlobalOptionsetMetadata join — see quirks guide #enums
  d.activefrom AS "Date the value becomes valid for posting",
  d.activeto AS "Date the value stops being valid for posting",
  d.backingrecorddataareaid AS "Company of the backing record, populated for company-specific dimension values",
  d.recid AS "The 64-bit surrogate key DimensionAttributeValueSetItem.DimensionAttributeValue joins to"
FROM <catalog>.<schema>.dimensionattributevalue d
-- Resolve DimensionAttribute (via DimensionAttribute): uncomment to join on its RecId surrogate key
-- LEFT JOIN <catalog>.<schema>.dimensionattribute dim ON dim.recid = d.dimensionattribute
;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. RecId and InventDim edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

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

Data Entities That Expose This Table

No standard export entity — land the raw framework tables to decode dimensions.

Browse more finance tables