Week 6 of 8
Integrations, SIT and UAT
Dual-write links Finance and Operations to Dataverse in near real time and in both directions: change a customer in one and the account changes in the other. That is powerful, and it means a CRM change can break an ERP process. Add banks, EDI partners, tax engines and warehouse apps, and integrations become the most likely place for a go-live to fail.
In Business Central, remember that a production copy blocks outbound calls and disables integrations by default. A SIT run in that sandbox proves nothing about the interface until you switch it back on, on purpose.
This week: make SIT end-to-end and UAT signable
- List every integration: direction, mechanism (dual-write map, data entity, OData, file, API), owner, partner contact, and monitoring.
- Write SIT as end-to-end chains, e.g. CRM quote → sales order in F&O → warehouse pick → invoice → bank payment → settlement, with a checkable result at each step.
- Test dual-write in both directions, including initial sync and what happens when the map is paused and catches up.
- Agree the UAT sign-off route now: process owner, functional lead, test manager, program director.
Number of the week
Blocked
is the default for outbound HTTP calls from extensions in a Business Central sandbox; each extension must be allowed explicitly.
Source: Microsoft Learn, Business Central environmentsUse this week
- SIT Cycle Plan & Entry/Exit Criteria →
End-to-end scenarios, sequence and testers for each cycle, with live progress counts.
- UAT Sign-Off Form (Word) →
Results, accepted defects and signatures for each process owner.
- Microsoft: dual-write overview →
What syncs, in which direction, and the play, pause and catch-up modes you need to test.
Next week: the Go-live Readiness Review and cutover. What evidence the room needs before anyone signs.
Get the playbook in your inbox, one week at a time
Subscribe free and every template in the library is yours.