D365 Reference
Dynamics 365 F&O Reference Database
F&O hands over raw columns, not meaning: every row keys on a 64-bit RecId, the company is just a DataAreaId value, and every quantity hangs off an opaque InventDimId that hashes one combination of site, warehouse, location, batch, and serial. A searchable reference for landing F&O data through Synapse Link or Fabric Link, with a quirks guide for what a first extract gets wrong.
Free & ungated · Last verified October 2026
- Tables
- 63
- Entities
- 26
- Modules
- 10
- Quirks
- 10
How this is scoped
- Scope: the supply-chain core — product, inventory, sales, procurement, production, warehouse management, and master planning — plus the shared party and financial-dimension foundations every table points back to. The catalog spans 63 tables and 26 data entities today and is still growing; it leads with the objects an analyst reaches for most, not a full metadata dump.
- Feeds: the business-problem grid draws on this reference for Inventory & Working Capital, Demand Planning & Forecasting, Customer Service & Fulfillment, Procurement & Supply and Manufacturing & Production.
- Two axes: F&O exposes data both as raw tables and as export-shaped data entities. This reference documents both — the tables you land, and the entities that expose them — because some core objects (InventTrans, InventSum, DirPartyTable) have no standard export entity and must be landed raw.
- Verification: field names, keys, and structural facts are curated against the Microsoft CDM schema pages; enum integer values ship only when verified, and every description is original wording. Last verified October 2026.
- Built for analytics: relationships focus on the joins you’ll actually write — header/line pairs, shared-EDT foreign keys, RecId surrogate references, and the InventDim dimension hop that trips up every first on-hand query.
Frequently Referenced Tables
The workhorses of F&O supply-chain analytics — the inventory ledger and on-hand, sales orders, the item master, and the customer master.
- 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
- InventTransThe inventory transaction ledger — every physical and financial stock movement, with issue/receipt status, quantities, dates, and links back to its source document
- InventSumAggregated on-hand quantities by item and inventory dimension — physical, available, and posted balances
- SalesLineSales order line — one row per order line; the core sell-side transaction, joined to its header by SalesId
- SalesTableSales order header — one row per order carrying customer, status, site, and requested dates
- PurchLinePurchase order line — one row per order line; the core buy-side transaction, joined to its header by PurchId
- InventDimThe inventory dimension hub — one row per unique combination of site, warehouse, location, batch, and serial that every stock quantity hangs off by InventDimId
- CustTableCustomer master — one row per customer account, with the RecId links to its global-address-book party and its default financial dimensions
- ProdTableProduction order header — one row per order carrying the item being built, order status and type, scheduled and actual dates, and the BOM and route it was created from
- VendTableVendor master — one row per vendor account, with the RecId link to its global-address-book party
Frequently Used Data Entities
The export-shaped surfaces behind the order-to-cash and procure-to-pay data — what a Synapse Link or OData export gives you.
- EcoResReleasedProductV2EntityReleased products — the item master joined to its shared product, the standard export for item attributes
- SalesOrderHeaderV2EntitySales order headers — one record per order, the header-level export for order-to-cash
- SalesOrderLineV2EntitySales order lines — one record per order line, the line-level export joined to its header
- CustCustomerV3EntityCustomers — the customer master joined to its address-book party, the standard customer export
- VendVendorV2EntityVendors — the vendor master joined to its address-book party, the standard vendor export
- PurchPurchaseOrderHeaderV2EntityPurchase order headers — one record per order, the header-level export for procure-to-pay
- PurchPurchaseOrderLineV2EntityPurchase order lines — one record per order line, the line-level export joined to its header
- ProdProductionOrderHeaderEntityProduction orders — one record per production order header, the standard export for order status, quantities, and schedule dates
The F&O quirks guide
The encoding and modeling traps that make a first F&O extract wrong in ways that look right. Each links to a worked Databricks SQL pattern.
Read all 10 quirksGetting F&O into your lakehouse
Export to Data Lake is retired. The extraction guide covers the current paths — Fabric Link, plus time-limited Synapse Link Delta for existing customers and Synapse Link CSV for incremental change needs — the metadata columns they add, soft deletes and incremental MERGE patterns, and when to land raw tables vs entity-shaped exports.
Read the extraction guideBrowse by Module
Organized by functional area. Click a module to see its tables and data entities.
- Product InformationThe shared product master and its released-product records, dimensions groups, and units of measure that every inventory and order table points back to12 tables · 7 entitiesSupply chain
- InventoryOn-hand balances, the inventory transaction ledger, dimension records, and warehouse/location master data11 tables · 3 entitiesSupply chain
- Sales & MarketingSales orders from header through line, plus the customer master on the sell side of order-to-cash8 tables · 6 entitiesSupply chain
- Procurement & SourcingPurchase orders and the vendor master across the procure-to-pay cycle7 tables · 3 entitiesSupply chain
- Production ControlProduction orders, BOMs, and routes that define how items are manufactured8 tables · 2 entitiesSupply chain
- Master PlanningPlanned orders, requirement transactions, and forecasts that translate demand into planned supply2 tables · 0 entitiesSupply chain
- Warehouse ManagementAdvanced warehouse work, loads, shipments, and directed put-away and picking inside the four walls5 tables · 3 entitiesSupply chain
- FinanceThe financial-dimension framework and ledger records the supply-chain tables reference for accounting and reporting6 tables · 1 entities
- Organization AdministrationLegal entities (companies), sites, and the shared organizational setup that defines DataAreaId partitioning2 tables · 1 entities
- Global Address BookThe shared party registry (DirPartyTable) behind every customer, vendor, and organization record2 tables · 0 entities
Sources & further reading
Table structure, entity names, and extraction behavior are authoritative only at source. Use these references to verify before building on any claim in this reference.
Show all 16 sources, graded by group
Microsoft official
- Microsoft CDM schema — Operations tables (opens in new tab) — the version-tagged field lists per F&O table (the primary source this catalog is curated against).
- Microsoft CDM schema — Operations entities (opens in new tab) — the per-entity pages with attributes and backing-table declarations; the primary source for the entity names and table-entity mappings in this catalog.
- Dynamics 365 data entities documentation (opens in new tab) — what data entities are, how they're categorized, and the entity properties (public collection name, OData exposure) this reference reports.
- Synapse Link — finance and operations data (opens in new tab) — how F&O tables land in ADLS Gen2, including metadata columns and documented column renames.
- Fabric Link documentation (opens in new tab) — linking Dataverse (including F&O data) to Microsoft Fabric via OneLake, with no storage account to operate.
- Synapse Link — choice (option set) labels (opens in new tab) — the OptionsetMetadata / GlobalOptionsetMetadata table schemas behind the enum-decode pattern in the quirks guide, including the LocalizedLabelLanguageCode = 1033 convention.
- Removed or deprecated F&O platform features (opens in new tab) — the current register for Export to Azure Data Lake's November 1, 2024 retirement and November 30, 2026 permanent stop.
- Dynamics 365 release plans (historical) (opens in new tab) — release-wave content retained for historical reference after Microsoft stopped publishing new release plans in September 2026.
- Microsoft AI at Work roadmap (opens in new tab) — Microsoft's stated successor to release plans for new Dynamics 365, Power Platform, and Dataverse capabilities beginning in September 2026. As of September 2026 it is a Microsoft 365-branded roadmap with no dedicated Dynamics 365 filter, so past release waves are still looked up in the retained release plans above. Each specific gate still cites its own documentation page.
- Configure Link to Microsoft Fabric (opens in new tab) — current F&O build gates, workspace-identity authentication, table limits, low-latency migration, Change Data Feed, and preview SQL endpoint metadata sync.
- Synapse Link Delta Lake export (opens in new tab) — Delta/Parquet lifecycle deadlines, Spark runtime requirements, conversion intervals, and in-place profile upgrades.
- Row version change tracking (opens in new tab) — the SysRowVersion table prerequisite, entity eligibility rules, and deletion-tracking behavior behind incremental exports.
- Microsoft CDM repository — Operations definitions (opens in new tab) — a machine-readable historical provenance fallback for exact structures. Pin the commit used for an audit; the repository does not attest every current application release.
Databricks official
- Lakeflow Connect — Microsoft Dynamics 365 (opens in new tab) — the managed connector's supported source paths, table ceiling, SCD2 behavior, and schema-evolution boundaries.
- Lakeflow Connect — Dynamics 365 limitations (opens in new tab) — retention, full-refresh recovery, column backfill, SCD2 scheduling, schema-change, and attachment-content limits.
Practitioner corroboration
- Dynamics 365 Community (opens in new tab) — practitioner questions and operational corroboration. Never the sole authority for a shipped enum, entity name, or vendor-behavior claim.