D365 Reference
CustCustomerGroupEntity
OData: CustomerGroupsCustomer groups — the posting/reporting group master, the standard export for group codes and their default terms
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
Research-confirmed; OData collection CustomerGroups.
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
3 parameters not filled: <catalog>, <schema>, <company>
-- ============================================================
-- Entity : CustCustomerGroupEntity (OData: CustomerGroups)
-- Purpose: Rebuild CustCustomerGroupEntity from landed F&O tables — auto-generated from table-entity-map
-- Grain : One row per CustGroup record
-- Tables : CustGroup
-- 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.custgroup AS "The customer group code — the natural key CustTable.CustGroup joins on",
h.name AS "Descriptive name of the customer group"
FROM <catalog>.<schema>.custgroup h
WHERE
h.dataareaid = '<company>'
ORDER BY h.custgroup;