D365 Reference
EcoResTrackingDimensionGroupEntity
Tracking dimension groups — the shared batch/serial activation setup, one record per group
Tables vs entities
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
Notes
CDM-confirmed; backing table EcoResTrackingDimensionGroup declared.
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.
Query parameters
2 parameters not filled: <catalog>, <schema>
-- ============================================================
-- Entity : EcoResTrackingDimensionGroupEntity
-- Purpose: Rebuild EcoResTrackingDimensionGroupEntity from landed F&O tables — auto-generated from table-entity-map
-- Grain : One row per EcoResTrackingDimensionGroup record
-- Tables : EcoResTrackingDimensionGroup
-- 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 tracking dimension group name — the natural key products reference through their group assignment",
h.description AS "Description of the group"
FROM <catalog>.<schema>.ecorestrackingdimensiongroup h
ORDER BY h.name;