Dynamics 365 Business Central Page Scripting GA Adds Multi-Row and Dialog Text Testing

Roadmap item 573384 identifies the Web platform and Worldwide (Standard Multi-Tenant) cloud. That scope matters: it should not be read as confirmation that every deployment has already received the update. Microsoft describes its roadmap dates as estimates that remain subject to change.

What changes at general availability​

Microsoft’s roadmap description groups the update into three areas:

• Multi-row selection: Recordings can capture selections involving several grid rows.
• Dialog-text validation: Tests can check the wording displayed in message and error dialogs.
• Interface improvements: The tool is described as fully localized, with accessibility, usability, and visual refinements.

The entry does not enumerate supported languages, individual accessibility changes, dialog-matching rules, or a minimum Business Central build. Those details should not be inferred from the GA label.

Bulk workflows get a more representative test​

The multi-selection addition addresses a concrete documented weakness. Microsoft Learn’s preview documentation warns that when several records are selected, only the final selection is recorded and replayed. The new capability therefore targets an existing obstacle to testing bulk actions—not simply another convenience button.

For test owners, the practical next step is to revisit scenarios previously excluded because they depended on selecting several records. An illustrative acceptance test would select a known group, perform an applicable action, and verify the intended outcome for that group.

That is a suggested test design, not a guarantee that every grid action behaves identically. Start with representative data and confirm what the recording actually replays.

Dialog checks make outcomes more meaningful​

There is an important difference between reaching a dialog and receiving the right dialog. The announced text-validation capability gives test authors a way to check user-facing outcomes, including expected errors.

A useful proposed scenario is deliberately supplying invalid input and checking that the intended error appears. The value lies in the assertion: “the workflow reached this point” becomes “the application reported the expected result.”

However, the roadmap does not establish whether matching is exact, partial, or otherwise configurable. It also does not explain how text assertions behave when the client language changes. Multilingual test suites should treat those as questions to validate, not assumptions to bake into every recording.

Getting started with an acceptance recording​

Microsoft Learn documents this basic workflow:

1. Confirm recording permission: PAGESCRIPTING - REC, or equivalent. Playback requires PAGESCRIPTING - PLAY, or equivalent.
2. Open Settings > Page Scripting.
3. Select Start new, perform the business task, and select Stop.
4. Select Play to replay it, then Save to retain the recording as YAML.

Playback shows green checkmarks for successful steps and red failure indicators. Microsoft recommends a known starting location, dependable test data, and smaller recordings. Playback begins from the current page; stepping backward does not undo changes.

As an operational precaution, trial recordings against controlled test data before replaying workflows that change business records. A recorder is not an undo button wearing a nicer jacket.

GA does not mean universal browser automation​

Page Scripting targets Business Central interactions arising from AL execution. Microsoft explicitly excludes control add-ins, embedded Power BI reports, and activity outside the Business Central web client. It is not a general-purpose HTML automation tool.

Nor are all its capabilities new this month. Microsoft’s October 3, 2025 release-plan entry already covered improved insertion, step rearrangement and deletion, UI-defined parameters, and script composition. Those are earlier authoring enhancements, distinct from this GA announcement.

Pipeline replay also predates the milestone: Microsoft introduced the standalone bc-replay player for CI/CD use in the 2024 release wave 2. Teams can therefore consider automated execution without presenting it as a newly announced October 2026 feature.

The practical takeaway​

The strongest reason to revisit Business Central Page Scripting is the expanded test coverage: bulk selections and expected dialog content are meaningful parts of real business processes.

Prioritize a small set of those scenarios, confirm the capabilities in the target environment, and inspect both the replay results and business outcomes. General availability is a product milestone; a trustworthy acceptance suite still needs carefully chosen data and checks.