DimensionAttributeValueSetItem
referenceShared across companiesOne row per dimension value inside a stored value set — the line level of DimensionAttributeValueSet, carrying the value's display code denormalized for fast decodes
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/ValidToeffectivity window — a join without a date filter multiplies every key by its history (see the quirks guide).
Header & line
DimensionAttributeValueSetItem lines join back to their header DimensionAttributeValueSet — and the DataAreaId — so a line never fans out across companies.
Fields
4 fields · 2 key
4 fields.
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | DimensionAttributeValueSet | RecId | RecId of the value set this line belongs to — join from a master's DefaultDimension to explode the set into rows | int64 | ||
| Key | DimensionAttributeValue | RecId | RecId of the dimension value on this line — the hop to DimensionAttributeValue and on to DimensionAttribute for the dimension name | int64 | ||
| DisplayValue | The value code stored denormalized on the line — often all a decode needs once you know the dimension | string | ||||
| BackingRecordDataAreaId | Company of the value's backing record, populated for company-specific dimension values | string |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading DimensionAttributeValueSetItem 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.
2 parameters not filled: <catalog>, <schema>
-- ============================================================
-- Table : DimensionAttributeValueSetItem One row per dimension value inside a stored value set — the line level of DimensionAttributeValueSet, carrying the value's display code denormalized for fast decodes
-- Purpose: Column-selected read of DimensionAttributeValueSetItem — auto-generated from field metadata
-- Grain : One row per DimensionAttributeValueSet + DimensionAttributeValue
-- 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.dimensionattributevalueset AS "RecId of the value set this line belongs to — join from a master's DefaultDimension to explode the set into rows",
d.dimensionattributevalue AS "RecId of the dimension value on this line — the hop to DimensionAttributeValue and on to DimensionAttribute for the dimension name",
d.displayvalue AS "The value code stored denormalized on the line — often all a decode needs once you know the dimension",
d.backingrecorddataareaid AS "Company of the value's backing record, populated for company-specific dimension values"
FROM <catalog>.<schema>.dimensionattributevaluesetitem d
-- Resolve DimensionAttributeValueSet (via DimensionAttributeValueSet): uncomment to join on its RecId surrogate key
-- LEFT JOIN <catalog>.<schema>.dimensionattributevalueset dim ON dim.recid = d.dimensionattributevalueset
-- Resolve DimensionAttributeValue (via DimensionAttributeValue): uncomment to join on its RecId surrogate key
-- LEFT JOIN <catalog>.<schema>.dimensionattributevalue dim ON dim.recid = d.dimensionattributevalue
ORDER BY d.dimensionattributevalueset;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
ON dimensionattributevaluesetitem.dimensionattributevalueset = dimensionattributevalueset.recidON dimensionattributevaluesetitem.dimensionattributevalue = dimensionattributevalue.recid
Data Entities That Expose This Table
More Finance tables
- VendTransThe vendor transaction ledger — one open-item row per posted AP amount (invoice, payment, credit note), mirroring CustTrans on the payable side; the table AP aging and DPO are built from, companion to the VendInvoiceJour invoice detail
- CustTransThe customer transaction ledger — one open-item row per posted AR amount (invoice, payment, credit note), carrying signed amounts, due date, and settlement state; the table AR aging and DSO are built from, companion to the CustInvoiceJour invoice detail
- DimensionAttributeThe registry of financial dimensions themselves (cost center, department, business unit…) — one row per dimension, recording which table or view backs its values
- DimensionAttributeValueOne 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
- DimensionAttributeValueSetA stored set of financial-dimension values referenced by masters and transactions via a RecId; the first hop when decoding default dimensions into columns