D365 Reference

CustCustomerV3Entity

OData: CustomersV3

Customers — the customer master joined to its address-book party, the standard customer export

Module: Sales & Marketing
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

V3 customer entity; research-confirmed.

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 : CustCustomerV3Entity (OData: CustomersV3)
-- Purpose: Rebuild CustCustomerV3Entity from landed F&O tables — auto-generated from table-entity-map
-- Grain  : CustTable × DirPartyTable — 1:N joins yield one row per line
-- Tables : CustTable, DirPartyTable
-- 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
  c.accountnum AS "The customer account number — the natural key",
  dp.partynumber AS "The global-address-book party number"
FROM <catalog>.<schema>.custtable c
LEFT JOIN <catalog>.<schema>.dirpartytable dp
  ON dp.recid = c.party
WHERE
  c.dataareaid = '<company>'
ORDER BY c.accountnum;

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

Backing Tables

How these tables connect. Nodes are clickable.

Join details