D365 Reference

InventOperationalSiteEntity

Operational sites — the site master export, one record per site with its time zone, default status, and primary address flattened into columns

Module: Inventory
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-verified; backing table InventSite (BackingTable_InventSiteRelationshipId on the CDM page). CDM display name: Sites. No version suffix.

Rebuild-from-tables SQL

Databricks SQL

Starting 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
-- ============================================================
-- Entity : InventOperationalSiteEntity
-- Purpose: Rebuild InventOperationalSiteEntity from landed F&O tables — auto-generated from table-entity-map
-- Grain  : One row per InventSite record
-- Tables : InventSite
-- 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.siteid AS "The site code — the top inventory dimension; other tables reference it as InventSiteId",
  h.name AS "Site name"
FROM <catalog>.<schema>.inventsite h
WHERE
  h.dataareaid = '<company>'
ORDER BY h.siteid;

3 parameters not filled: <catalog>, <schema>, <company>

Backing Tables