DimensionAttributeEntity
Financial dimensions — one record per dimension with its name, backing view, and report column, the export for the dimension registry itself
This entity is an export-shaped view over the tables below. When you land raw F&O tables instead of the entity, the SQL further down rebuilds it — joining the backing tables on their keys and DataAreaId. When to land tables vs entities →
CDM-verified (entity version 1.1, since 10.0.13); backed by DimensionAttribute via RecId. OData public collection name is not on the CDM page, so it is omitted here — verify at Phase 2 sign-off.
Rebuild-from-tables SQL
Databricks SQLStarting point for reconstructing this entity from landed tables — the backing tables joined on their keys and DataAreaId. Set your Unity Catalog location, company, and filter values below.
-- ============================================================
-- Entity : DimensionAttributeEntity
-- Purpose: Rebuild DimensionAttributeEntity from landed F&O tables — auto-generated from table-entity-map
-- Grain : One row per DimensionAttribute record
-- Tables : DimensionAttribute
-- 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. Company-partitioned tables are joined on DataAreaId to prevent cross-company fan-out. System/audit columns omitted — see the quirks guide.
-- ============================================================
SELECT
h.name AS "The dimension's name (CostCenter, Department, BusinessUnit…) — the natural identifier analysts pivot decoded columns on",
h.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)",
h.viewname AS "Name of the generated database view that exposes this dimension's values"
FROM <catalog>.<schema>.dimensionattribute h
ORDER BY h.name;2 parameters not filled: <catalog>, <schema>