# D365 Finance and Supply Chain One Version Update Test Checklist > Source: https://netray.co/tools/d365-one-version-update-test-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer A repeatable checklist for testing each Dynamics 365 service update in a sandbox before production, including regression, extensions, integrations and rollback readiness. ## Category microsoft-dynamics ## Erp Microsoft Dynamics 365 Finance and Supply Chain ## Audience - D365 F&O administrator - D365 F&O consultant - Test lead ## Tool **Kind:** checklist **Groups:** #### Plan and prepare **Items:** **Text:** Review the release notes and release plans for the target update and list changes that touch your modules **Critical:** true Confirm the update schedule and the maintenance window with business owners Check whether you need to pause an update and record the approval and the planned resume date **Text:** Name a test lead and a business sign-off owner for each module **Critical:** true Review the feature management workspace for features that become mandatory or default Confirm sandbox data is recent enough to test real scenarios #### Sandbox update and baseline **Items:** **Text:** Apply the update to a sandbox first and record the duration and any errors **Critical:** true Capture a baseline of key reports, balances and integration outputs before the update Check that batch jobs and integrations are in the expected state after the sandbox update Verify user access still works for sample users from every role Confirm that environment-specific settings, such as endpoints, are correct #### Regression testing **Items:** **Text:** Run the automated regression suite built with Task recorder and Regression suite automation tool where available **Critical:** true **Text:** Manually test the top business processes: order to cash, procure to pay, plan to produce, record to report **Critical:** true Test production order flow end to end: create, estimate, schedule, release, start, report finished, end Test master planning on a representative item set and compare to the baseline Test financial period close steps and key financial reports Test printed documents and custom report outputs, such as invoices and packing slips Test mobile or warehouse devices and shop floor screens used in production #### Extensions and integrations **Items:** **Text:** Compile and test all extensions and check for breaking changes in the API surface **Critical:** true **Text:** Run integration tests with every connected system: MES, EDI, banking, tax and BI **Critical:** true Check data entities used in integrations for version changes and deprecations Test Power BI, Excel add-in and data export scenarios Review customizations that depend on overridden or replaced standard behavior #### Security, performance and data **Items:** Check new or changed security privileges and update custom roles as needed **Text:** Run key batch jobs and compare runtimes to the baseline for regressions **Critical:** true Check key forms and inquiries for performance changes under realistic data volume Verify data management projects and recurring integrations still run #### Go/no-go and production update **Items:** **Text:** Log every defect with severity, owner and decision to fix, defer or accept **Critical:** true Hold a go/no-go meeting with the business sign-off owners and record the decision Communicate the production window, user impact and contacts to all users Pause or schedule batch jobs and integrations that should not run during the update **Text:** After production update, run a smoke test of critical processes before opening to users **Critical:** true Review the production health after go-live for the first days and capture lessons learned **Scoring Note:** Run the full list for each update, scaled to the content of the release. Critical items that are unchecked should block a go decision until a named owner accepts the risk. ## Content **Intro:** Dynamics 365 Finance and Supply Chain follows the One Version model, with continuous service updates that all customers take within supported windows. Testing each update in a sandbox before production is how teams avoid surprises. This checklist gives you a repeatable plan. **Sections:** #### How to use the checklist **Body:** Copy the list into your update runbook and assign owners. Scale the depth of testing to the release content: a small quality update may need a smoke test and your automated suite, while a release with changes in planning or costing needs deeper testing. Record results for each item and keep the evidence for audit. **Bullets:** - Start from the release notes for your modules - Automate the processes you repeat every update - Keep an owner and date next to every open item - Archive results as the update record #### Why a regression suite pays off **Body:** Because updates arrive regularly, manual retesting of everything does not scale. Task recorder can capture business processes as recordings, and the Regression suite automation tool can replay them against a sandbox using test cases stored in Azure DevOps. Start with the ten processes that would hurt most if they broke, and expand over time. Maintain the suite whenever setup or forms change. #### Extensions and integrations **Body:** Extensions built with the supported extensibility model usually survive updates, but compile errors and behavior changes still happen. Treat each connected system as a test case: send a real message through and confirm the result on both sides. Pay special attention to anything that reads data entities or depends on specific field values, as these are common sources of quiet breakage. #### Common mistakes **Body:** Frequent issues are testing in a sandbox with stale or thin data, skipping integrations because the partner team is not available, treating the update as an IT task without business sign-off, and not retesting batch runtimes. Another mistake is pausing updates repeatedly until a larger jump becomes riskier. **Cta:** If you want help turning your regression scenarios and data checks into a repeatable, private test aid on your own infrastructure, we can scope that with you. **Faq:** #### What does One Version mean for D365 F&O? **Answer:** It means all customers run the same code line, with service updates delivered continuously. Customers must stay within the supported update window, though a limited pause option exists. Check current Microsoft guidance for the exact schedule and rules. #### What is RSAT? **Answer:** The Regression suite automation tool replays recorded business process tasks from Task recorder against an environment, using test cases managed in Azure DevOps. It reduces manual regression effort, but recordings need maintenance when processes or forms change. #### Do I need to test every module after each update? **Answer:** Not at the same depth. Review the release notes, test what changed and your highest-risk processes deeply, and run a smoke test on the rest. Over time, an automated suite lets you cover far more with less effort. #### What should be in a go/no-go decision? **Answer:** Include open defects by severity, results of regression and integration tests, batch runtime comparisons, status of extensions, readiness of users and support, and a named business owner who accepts the remaining risk. Record the decision and its date. ## Search terms d365 one version update checklist, d365 service update testing, dynamics 365 finance update regression test, d365 rsat regression suite automation, d365 update sandbox test plan, d365 monthly update process, d365 f&o release readiness checklist, d365 pause update checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json