Topical authority hub

ERP Write-Back & Integration

The mechanism every Optimizer shares: read the system of record, compute the decision, write it back behind a human approval step.

Dynamics 365 write back integration
Articles
14
Total read
126m
Pillar
Set
Start here — foundational guide
PillarFoundational guide

Your optimizer is only as good as its write path. How should it read and write Dynamics 365?

Microsoft's integration overview for finance and operations apps publishes six integration patterns, and two of those six rows are containers holding several documented surfaces each. This is the map an IT buyer should hold before any companion app touches the ERP — what each surface is for, which limits are actually enforced today, what a read costs versus a write, and the thirteen narrower questions underneath this one.

Muhammad Mudassir12 minAug 1, 2026
Read the guide

Continue the path

Ordered by chapter. Each post stands alone but builds on the one before it.

Chapter 1

Why does your OData integration slow down at a few thousand records an hour?

Microsoft's own integration sizing examples put OData at a peak data volume measured in records per hour, and the batch data API examples two orders of magnitude above it. Here is the table Microsoft publishes, the caveat it attaches, the validate chain that explains the number, and the four OData behaviours that make a working integration slower or quietly wrong.

9 minRead
Chapter 2

Which Dynamics 365 service protection limits are actually enforced?

The per-user request ceiling everyone quotes for Dynamics 365 is still published, and Microsoft's own banner says the limits behind it are disabled on all environments with the option to enable them removed. Here is what the service protection API limits page says today, which limit type actually returns a throttling response, the priority control you can set, and why an exemption moves the meter rather than removing it.

9 minRead
Chapter 3

Why do recurring integrations create duplicate documents?

A duplicated document from a recurring integration is a redelivery, not a lost message. Microsoft documents that an unacknowledged message becomes available to dequeue again every 30 minutes until it is acknowledged, and that the acknowledgement must echo the dequeue response body. Here is the contract in Microsoft's words, the three ways teams break it, one more path that re-serves the same message, one upgrade that breaks your defence against it, and what will not fix any of it.

7 minRead
Chapter 4

Business events give you no ordering guarantee. What do you build instead?

Microsoft states it under a heading called Limitations - the order in which Finance and Operations emits business events isn't guaranteed to preserve the order in which they're delivered. The control number is a dedupe key, not a sequence. So you build consumers that are idempotent, derive state from the record rather than the event sequence, and reconcile against the ERP rather than against the event stream.

8 minRead
Chapter 5

Why do your data events never fire for some entities?

Microsoft names the class exactly - when a data entity uses a view as its primary data source, data events don't trigger. Not all views, not all entities - the entity's primary data source. This article gives Microsoft's wording and its stated reasons, the separate temporary-table case that raises an error instead of staying silent, and the published throughput figures that Microsoft says the environment does not explicitly throttle.

8 minRead
Chapter 6

What does dual-write actually cost you in transaction budget?

A budget with three published lines. Microsoft states a two-minute transaction time limit that includes the time to process standard and custom Dataverse plugins, a ceiling of 1,000 records per single transaction in the finance and operations to Dataverse direction, and a plan of record restricting dual-write to a one-to-one mapping. Every dual-write write spends from all three, and the bill arrives at posting time.

8 minRead
Chapter 7

Why are virtual tables fast in the demo and slow in production?

Because a demo has one entity, few rows and co-located environments, and production has none of those. Across the virtual entities overview, the virtual entities FAQ and the entity-modeling page, the only virtual entity overhead figure Microsoft publishes is for the co-located case; there is an FAQ answer headed "The virtual entity performance is slow when a virtual entity has relationships to other entities"; and Microsoft states that the exemption applies only to the Finance and Operations endpoints the virtual entity plugin invokes, and that because the request is made through the Dataverse API, Dataverse service protection limits might still apply to it.

8 minRead
Chapter 8

How do you move a million rows into Dynamics 365 without breaking it?

The answer is the Data management framework's package REST API, in batch — and the value is four operational facts the call itself never tells you: the caller cannot parallelise it, parallel package import is a precondition, the blob file lives seven days, and error retrieval is two-phase and polled with an ambiguous empty response. Each verified against Microsoft's page, operation names character-exact.

9 minRead
Chapter 9

Is BYOD retired?

Microsoft's transition FAQ answers this under its own heading, on a page revised in July 2026 — a retirement date for BYOD hasn't been determined, and Microsoft recommends transitioning in the same sentence. Both halves are the answer. Here are the five Microsoft pages checked, the four dates Microsoft documents for Export to Data Lake, why any single-date summary of it is wrong, and why a bounded no is still not a reason to stay.

8 minRead
Chapter 10

Did the Synapse trusted-services firewall exception retire on 1 August 2026?

The retirement was dated 1 August 2026. On the day, Microsoft's transition FAQ still states it in the future tense on a page revised in July, while a Microsoft Q&A answer describes a move to 2027. Here is what nine Microsoft pages say, the date each one carries, and what to check in your own tenant.

8 minRead
Chapter 11

Fabric link or Synapse Link — which analytics path for Dynamics 365 data?

Link to Fabric and Azure Synapse Link are not two flavours of the same service. In Microsoft's own comparison one keeps the data in Dataverse and consumes Dataverse storage, while the other exports to a storage account you own, and — on the delta-parquet profile Microsoft documents for finance and operations tables — needs a Synapse workspace and Spark pool to convert it. This is what each requires before it works, Microsoft's cost and freshness figures with the caveat Microsoft attaches to them, the one-way doors documented on each side, and the live networking dispute sitting under one of the two.

11 minRead
Chapter 12

Microsoft names six Dynamics 365 integration patterns. Which for which job?

Microsoft's integration overview for finance and operations apps publishes a table of six integration patterns, and two of those six rows are containers holding several documented surfaces each. This is the expansion, the synchronous-versus-asynchronous split, Microsoft's own volume rule of thumb and sizing examples with the caveat it attaches to them, and the one documented constraint that decides each pattern.

11 minRead
Chapter 13

What can't Dynamics 365 do natively for EDI?

Finance and Operations publishes a substantial electronic-document capability — a configurable format engine, an electronic invoicing service, inbound and outbound ASN objects, and file-based integration with transformation. What none of those pages documents is the EDI layer itself: encode and decode, trading partners and agreements, envelope control numbers, acknowledgements and the transports. Microsoft documents those, in Azure. This is the scoping brief, with the pages searched named against each gap.

10 minRead
Build it for real

Read the writeup. Now ship the system.

Cognilium engineers ship the architectures behind these articles for enterprise teams. If you're mid-build on erp write-back & integration, talk to us.