D365 Reference
SalesOrderHeaderV2Entity
OData: SalesOrderHeadersV2Sales order headers — one record per order, the header-level export for order-to-cash
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
V2 header entity; research-confirmed.
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 : SalesOrderHeaderV2Entity (OData: SalesOrderHeadersV2)
-- Purpose: Rebuild SalesOrderHeaderV2Entity from landed F&O tables — auto-generated from table-entity-map
-- Grain : One row per SalesTable record
-- Tables : SalesTable
-- 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
so.salesid AS "The sales order number — the natural key sales lines join back on",
so.salesname AS "Free-text order description"
FROM <catalog>.<schema>.salestable so
WHERE
so.dataareaid = '<company>'
ORDER BY so.salesid;