Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table
The Dynamics 365 Testing Playbook

Week 8 of 8

Staying current: service updates and RSAT

Finance and Operations ships four service updates a year. You can pause one at a time and must take at least two. The UAT sandbox updates seven days before production, and there is no rollback. Business Central ships two major updates a year with a five-month window to take each one.

Then there is tooling. Microsoft has marked the Regression Suite Automation Tool for deprecation, with no support after 15 May 2027. If your regression suite is RSAT and Task recorder files, you need an exit plan, while Business Central teams gain page scripting and command-line AL tests in version 29.

This week: fit regression to the calendar and plan the RSAT exit

  1. Put the next four F&O releases and the next BC major update on one calendar, with the date your regression must finish.
  2. Start regression on the generally available package in your own sandbox, not on the auto-update. That turns seven days into weeks.
  3. Inventory your RSAT test cases: process, owner, last run, pass rate, and whether the recording still matches the screen. Decide keep, rebuild or retire for each.
  4. Measure three things per update: critical process coverage, regression cycle time and escaped defects.

Number of the week

7 days

between the UAT sandbox update and the production update for finance and operations service updates.

Source: Microsoft Learn, One Version service updates FAQ

Use this week

That is the playbook. From next week you will get a weekly roundup of new statistics, guides and templates from The Sign-Off Table.

Get the playbook in your inbox, one week at a time

Subscribe free and every template in the library is yours.