D365 Reference
InventItemGroup
groupItem group master — one row per company and item group, the reporting and posting bucket items are assigned to via InventItemGroupItem
Module: Product InformationCompany-partitioned (DataAreaId)
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).
In field listings, K marks a key field.
Fields
3 fields · 1 key
3 fields.
| Key | Field | EDT | Description | Type | Length | Flags |
|---|---|---|---|---|---|---|
| Key | ItemGroupId | ItemGroupId | The item group code — the reporting bucket InventItemGroupItem assigns items into | string | ||
| Name | Item group name | string | ||||
| StandardItemAllocateId | Default item allocation key for forecast allocation over this group | string |
Field provenance: hand-curated.
Boilerplate SQL
Starting point for reading InventItemGroup 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
3 parameters not filled: <catalog>, <schema>, <company>
-- ============================================================
-- Table : InventItemGroup Item group master — one row per company and item group, the reporting and posting bucket items are assigned to via InventItemGroupItem
-- Purpose: Column-selected read of InventItemGroup — auto-generated from field metadata
-- Grain : One row per company (dataareaid) + ItemGroupId
-- 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
i.itemgroupid AS "The item group code — the reporting bucket InventItemGroupItem assigns items into",
i.name AS "Item group name",
i.standarditemallocateid AS "Default item allocation key for forecast allocation over this group"
FROM <catalog>.<schema>.inventitemgroup i
WHERE
i.dataareaid = '<company>'
ORDER BY i.itemgroupid;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 inventitemgroupitem.itemgroupid = inventitemgroup.itemgroupid AND inventitemgroupitem.itemgroupdataareaid = inventitemgroup.dataareaidON inventitemgroupitem.itemgroupdataareaid = inventitemgroup.dataareaid
Data Entities That Expose This Table
No standard export entity confirmed — land the raw table alongside InventItemGroupItem to resolve item-to-group assignments.
More Product Information tables
- InventItemGroupItemThe link table that assigns each released item to its item group — in D365 the item group is NOT a column on InventTable; this table is where the assignment lives. Cross-company: it carries explicit ItemDataAreaId / ItemGroupDataAreaId columns instead of a DataAreaId partition
- InventModelGroupItem model group master — one row per company and model group, controlling inventory policy for its items: costing model, negative-stock rules, and whether the product is stocked at all
- InventModelGroupItemThe link table that assigns each released item to its item model group — like the item group, the model group is not a column on InventTable. Cross-company, with explicit ItemDataAreaId / ModelGroupDataAreaId columns
- InventTableReleased product master — one row per item within a company, carrying the RecId link to its shared product; item group and model group are assigned in the InventItemGroupItem / InventModelGroupItem link tables, not here
- InventTableModulePer-module item settings — one row per released item per module (inventory, purchase, sales), holding that module's default unit, base price and price unit, discount groups, tax item group, and over/under-delivery tolerances; a fully set-up item normally has exactly three rows per company
- UnitOfMeasureThe shared unit-of-measure master — one row per unit symbol (kg, ea, hr) with its unit class and system of units; every quantity column in the lake ultimately resolves to a symbol here