D365 Reference

OMLegalEntity

Legal entities — one record per company with its registration details and flattened primary address and contact information, the export behind the company list

Module: Organization Administration
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 (entity version 1.1, since 10.0.13); primary datasource CompanyInfo. OData public collection name (commonly cited as LegalEntities) is not on the CDM page, so it is omitted here — verify at Phase 2 sign-off.

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 : OMLegalEntity
-- Purpose: Rebuild OMLegalEntity from landed F&O tables — auto-generated from table-entity-map
-- Grain  : One row per CompanyInfo record
-- Tables : CompanyInfo
-- 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.dataarea AS "The company code this legal entity owns — the natural join to DataArea and to every table's dataareaid",
  h.name AS "Legal-entity name, inherited from the company's address-book party record"
FROM <catalog>.<schema>.companyinfo h
ORDER BY h.dataarea;

2 parameters not filled: <catalog>, <schema>

Backing Tables