AI, in your work.

What changes

On October 23, 2026, Microsoft merged a Subscription Billing correction into the main branch of BCApps. Commit 15385de replaces Error(ErrorText) with Error(ErrorTextInfo) in two error handlers used during document creation. BCApps change.

The DisplayOrLogErrorFromBillingTemplate and DisplayOrLogErrorFromBillingLine procedures already populated the object now being used. It includes RecordId, SystemId and TableId; for the template, those identifiers are assigned if the record is found. The automated billing branches continue logging errors without raising the interactive error. Handler implementation.

The limit: navigation remains unproven

The commit description presents navigation as the intended outcome. However, these handlers configure neither PageNo nor AddNavigationAction. Preserving identifiers does not, by itself, demonstrate that a button capable of opening the record will appear. Reviewed implementation.

Microsoft documents AddNavigationAction as a mechanism for adding a Show-it action to the dialog. Error(ErrorInfo), meanwhile, displays the error and stops AL execution: using it does not automatically correct the data or update the billing proposal. Navigation action, Error(ErrorInfo) behavior.

What the added test covers

BillingTemplateErrorInfoContainsRecordIdOnUpdateRequired triggers an interactive failure with a line marked Update Required. It checks that GetLastErrorCode() is nonempty and that the message contains Update Required. Its assertions neither compare the RecordId nor open a page. The change adds no dedicated case for the billing-line handler. The file also declares TestPermissions = Disabled: this test does not establish behavior under an operational user's permissions. Nexo reviewed the code without running the test. Regression test.

Availability: integration and distribution are separate steps

The PR is marked as merged and assigned to the Version 30.0 milestone. That milestone records a planning target; it does not establish deployment to customers. PR #10477, Version 30.0 milestone.

As of November 7, 2026, the sources consulted do not identify a shipped build containing this correction or confirm its presence in a tenant. The public update history reviewed contains no entry for reference 646836 associated with the change; that absence does not establish that it has not been distributed through another route. Microsoft update history.

Nexo's interpretation

Preserving record identity may help diagnosis. Our interpretation is that functional acceptance should also examine what the person can do after the error: understand the cause, locate the record and continue investigating with their usual permissions. Any reduction in support time would require measurement; we do not present it as an outcome of this correction.

A synthetic example for functional review

Proposed checks, not executed: a test company uses contract SUS-010, template MENSUAL and line L-01. These identifiers are invented. Before evaluating the change, confirm that the build being used contains it. The table describes what to observe without predicting results.