AI, in your work.

A change merged into the repository

Microsoft merged PR #9045 into BCApps main on October 26, 2026. The commit message connects native AL XML with enabling partners to develop cloud-ready apps.

Configuration packages help prepare and transfer company setup data. Microsoft documents exporting them as .rapidstart files or Excel workbooks, providing context for teams maintaining automation and extensions around these operations. Microsoft documentation.

The diff clarifies the scope

The description presents a refactoring of codeunit 8618, Config. Excel Exchange. However, the change in that file is specific: it replaces the ImportPackageXMLFromStream call with ImportPackageXML. The broader XML transformation appears in codeunit 8614, Config. XML Exchange, and related objects, including background import. Commit diff.

That distinction matters: Config. Excel Exchange retains DotNet types for Excel processing. Adding native XML paths does not demonstrate complete removal of that codeunit’s .NET dependencies. Config. Excel Exchange code at the commit.

Methods and events worth reviewing

These three points can be verified in Config. XML Exchange. The cited legacy variants remain under #if not CLEAN30 and carry Obsolete attributes tagged 30.0.

Existing tests and availability

The author reports a local build without new analyzer warnings; the Business Central execution checkbox is unchecked. Commit message. The code includes tests for the renewed paths, covering import, export and metadata preservation. Their presence alone does not establish successful outcomes. Package operations tests.

The PR is assigned to the Version 30.0 milestone. This is a planning reference: merging into main and adding obsolescence tags do not confirm a shipped commercial release or installation in a tenant. Such availability was not established in this review. PR and milestone.

Nexo’s interpretation and functional limits

Our interpretation is that AL teams should review both signatures and execution paths. A legacy event remaining declared does not demonstrate that its subscriber participates in the native path: for field attributes, that path invokes the replacement event. This warrants checking the specific customization without assuming that every extension becomes incompatible.

The functional documentation requires matching schema and version for all data to transfer correctly, along with direct permissions on the relevant tables. Microsoft also limits its recommended RapidStart use to initial company setup. These requirements remain relevant when designing checks. Preparing packages, applying packages.

An example using synthetic data

As an example proposed by Nexo, a test table could contain code NX-001, the text “Prueba & Nexo”, a decimal and a date. Once a build containing the change is available, the team could compare it with its reference environment. These checks were not run for this article.

• Compile the extension against each environment’s symbols and record errors and obsolescence warnings.
• Export and import within each environment using the same synthetic dataset; compare fields, values and metadata without requiring byte-for-byte identical files.
• Instrument the relevant subscribers and check when they execute and what changes they produce.
• Add malformed XML or invalid data cases and record error handling without predicting the outcome.