Connectors Microsoft Dynamics 365 Finance and Supply Chain

Microsoft Dynamics 365 Finance and Supply Chain data integration with Lima, in both directions.

Dynamics 365 Finance and Supply Chain Management is Microsoft's cloud ERP. Lima reads its data entities through the Data Management Framework and OData, or through Synapse Link and the Dataverse where the estate uses them, and writes back through OData entities so that Dynamics applies its validation.

SOURCEMicrosoft Dynamics 365 Finance a…Data Management Framework packages · OD…LIMA BACKBONEExtractfull · incremental · change captureCheckevery row valid, or an exception with a…Transform and load150+ operators · Python · loads on the…TARGETSPlanning applicationsKinaxis · o9 · Blue Yonder · IBP · OMPWarehouses and lakehousesSnowflake · Databricks · Fabric · S3 …Reporting and partnersPower BI · Tableau · EDI · filesRESULTS RETURN TO MICROSOFT DYNAMICS 365 FINANCE AND SUPPLY CHAIN · EACH WRITE CONFIRMED
How Microsoft Dynamics 365 Finance and Supply Chain fits the six Backbone steps. It is a source and a target: data comes out through the methods below, and results go back in with confirmation.
3
ways to read or write it
this connector
4
patterns supported
this connector
3
ways to run: SaaS, private cloud, on-premise
product
22 days
from contract to production
showcase estate
How Lima reads and writes Microsoft Dynamics 365 Finance and Supply Chain

Method by method.

Each method has a job. The first load uses the bulk method; the daily run uses the incremental or change-capture method; write-back uses the interface the system itself uses.

MethodWhat it doesWhen it is used
Data Management Framework packagesExports data entities as files on a schedule.Bulk reads.
OData entitiesReads and writes entities with change tracking.Deltas and write-back.
Synapse Link / Fabric link tablesReads the exported tables where the estate has enabled them.Near-real-time reads without load on the application.
What it covers

Objects and patterns.

The objects are the tables, views or records Lima reaches through the methods above. The patterns say how a copy is made and kept current.

ObjectPlain meaning
Released productsitems by legal entity
BOM versions and linesbills of material
Routes and operationsroutings
On-hand inventorystock by warehouse and location
Purchase and sales ordersdocuments and lines
Vendors and customerstrading partners
PatternSupported
Full loadYes
IncrementalYes
Change captureentity change tracking; Synapse Link tables
Streaming—
Write-backOData entities; response is the confirmation
What a planning application needs from Microsoft Dynamics 365 Finance and Supply Chain

The objects a first load is built from.

A planning dataset is assembled from these objects. The pair pages show how each planning application shapes them.

Planning objectSource objects in Microsoft Dynamics 365 Finance and Supply Chain
ItemsReleased products V2
Bills of materialBOM versions · BOM lines
RoutingsRoutes · Route operations
StockOn-hand inventory entity
Open purchase ordersPurchase order headers and lines
Open sales ordersSales order headers and lines
Production ordersProduction orders and BOM lines
ForecastsDemand forecast entries
Customers and suppliersCustomers V3 · Vendors V2
CalendarsWorking time calendars
Before you start

Prerequisites, then four steps.

The prerequisites are what the team that runs Microsoft Dynamics 365 Finance and Supply Chain grants. The four steps are the same for every connector.

  • An application user with the data entity roles in scope
  • Azure AD application registration
  • Where used: Synapse Link or Fabric link enabled by the administrator
Register the connectionEndpoint, credentials from the vault, and the method. The connection is tested and a failed test names the cause.
Choose the objects and the patternPick tables or objects from the discovered schema, and the pattern: full, incremental, change capture or streaming.
Run the first load with checks onEvery row is valid or becomes an exception with an owner. The run ends with a count and a control total per table.
Schedule it on the business calendarA run window with a deadline; pause, resume and replay if a check trips; the report after every run.
What happens to a bad record

Incoming data = valid records + exception records. A row that fails a check is kept, routed to the person who owns it with a deadline, and replayed once fixed. The load carries on with the valid rows and the report says exactly what was held back. How exceptions work →

Pair pages

Microsoft Dynamics 365 Finance and Supply Chain in a source-to-target path.

Each pair page covers one path end to end: objects out, model in, checks, cadence and the offer.

/connectors/microsoft-dynamics-365-to-kinaxis-maestro

Microsoft Dynamics 365 Finance and Supply Chain to Kinaxis Maestro

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/microsoft-dynamics-365-to-o9

Microsoft Dynamics 365 Finance and Supply Chain to o9 Solutions

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/microsoft-dynamics-365-to-blue-yonder

Microsoft Dynamics 365 Finance and Supply Chain to Blue Yonder Planning

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/microsoft-dynamics-365-to-sap-ibp

Microsoft Dynamics 365 Finance and Supply Chain to SAP Integrated Business Planning

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/microsoft-dynamics-365-to-omp

Microsoft Dynamics 365 Finance and Supply Chain to OMP

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/microsoft-dynamics-365-to-anaplan

Microsoft Dynamics 365 Finance and Supply Chain to Anaplan

Planning integration: first load, then net change on the planning calendar; the plan returns to the ERP.

Open the pair page →
/connectors/microsoft-dynamics-365-to-snowflake

Microsoft Dynamics 365 Finance and Supply Chain to Snowflake

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/microsoft-dynamics-365-to-databricks

Microsoft Dynamics 365 Finance and Supply Chain to Databricks

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/microsoft-dynamics-365-to-microsoft-fabric

Microsoft Dynamics 365 Finance and Supply Chain to Microsoft Fabric

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/microsoft-dynamics-365-to-bigquery

Microsoft Dynamics 365 Finance and Supply Chain to Google BigQuery

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/microsoft-dynamics-365-to-amazon-redshift

Microsoft Dynamics 365 Finance and Supply Chain to Amazon Redshift

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →
/connectors/microsoft-dynamics-365-to-azure-synapse

Microsoft Dynamics 365 Finance and Supply Chain to Azure Synapse Analytics

Landing and history: full history landed with a count check per table, then kept current.

Open the pair page →

3 more pair pages for Microsoft Dynamics 365 Finance and Supply Chain are listed in the directory.

Terms on this page

Plain meanings.

ConnectorA packaged way to read or write one kind of system, with its authentication, methods and prerequisites described.
Full, incremental, change capture, streamingFour ways to make and keep a copy: read everything; read what changed since last time; read changes from a log as they happen; consume events in small batches.
Write-backWriting a result into the system that owns it through its released interface; the system's response is the confirmation.
Control totalThe sum of a key amount column compared between source and target, along with the row count, at the end of a run.
Exception recordA row that failed a check: kept, routed to an owner, replayed once fixed.
Questions

Asked about this connector.

Does Lima install anything in Microsoft Dynamics 365 Finance and Supply Chain?

Lima connects from outside through the interfaces listed above with credentials your administrators grant. Where a vendor requires its own agent or add-on for a method, the prerequisites say so.

How is load on Microsoft Dynamics 365 Finance and Supply Chain kept in check?

Parallel reads are capped and the cap is agreed with the team that runs the system. Large reads run inside an agreed run window. Change capture keeps the daily volume small.

What do we see when a run finishes?

A report per run: rows in, rows out, control totals and variance per table, the exceptions held back and who owns them, and whether the deadline was met.

Can we start small?

Yes. Most estates start with one source, one target and one dataset, then add tables and patterns on the same connection.

Try Microsoft Dynamics 365 Finance and Supply Chain on your own estate.

A trial connects this system, runs a first load and ends with a reconciliation report. Your administrators see the prerequisites before anything is installed.