Microsoft Dynamics 365
The mid-market and divisional ERP of choice, and increasingly the second ERP inside a group that also runs SAP or Oracle.
01 What it holds
The data inside it
Ledger, inventory, production, sales and purchasing for a legal entity, exposed through Dataverse and entity stores rather than raw tables in the cloud versions.
LedgerJournalTrans, CustTable, VendTable, InventTable, SalesTable / SalesLine, PurchTable, InventTrans, plus Dataverse entities for the Customer Engagement side
02 Getting the data out
Extraction, and the keys that decide whether it joins
Export to Data Lake / Synapse Link is the supported path for F&O; Business Central exposes OData and APIs. Legacy AX and NAV estates are usually read directly from SQL Server.
DataAreaId is the company scope and appears on almost every table. Joins that omit it merge two legal entities into one set of numbers, which reconciles to nothing.
03 What goes wrong
The failures that look like success
Each of these produces a number that is plausible, reconciles to something, and is wrong. They are worth reading before the first extract, not after the first dispute.
DataAreaId omitted
The most common single defect in a Dynamics extract, and it produces plausible totals that are simply the sum of unrelated companies.
Two products under one name
Business Central and Finance & Operations share branding and almost no data model. Reusing a mapping between them does not work.
Financial dimensions are encoded
Cost centre, department and project live in a dimension combination that has to be resolved before a figure means anything by department.
Entity store latency
Aggregate measurements refresh on a schedule; treating them as live is how a dashboard ends up an hour behind the transaction it is describing.
04 Joins that matter
What this system is worth joining to
| Join to | What it lets you answer |
|---|---|
| Salesforce or D365 Sales | the same customer under two identities |
| WMS | inventory transactions against physical stock movement |
| Payroll | labour cost into production and project costing |
05 Metrics it feeds
The numbers that come out of it
06 Questions
Frequently asked
Is Dataverse a data platform?
It is an application data layer, not an analytics one. It is the right place to read from and the wrong place to build enterprise history and cross-system joins in.
How do we handle a group running both D365 and SAP?
Resolve the shared entities — customer, supplier, item, legal entity — before attempting a consolidated metric. Chart-of-accounts mapping alone gives you a consolidated number nobody can decompose.
Connect this system without replacing it
SCIKIQ reads it in place, resolves the entities inside it and governs what the fields mean.