Extension validation on upgrade
This content is archived and is not being updated. For the latest documentation, go to New and Planned for Dynamics 365 Business Central. For the latest release plans, go to Dynamics 365 and Microsoft Power Platform release plans.
|Enabled for||Public preview||General availability|
|Admins, makers, marketers, or analysts, automatically||Sep 1, 2021||Sep 1, 2021|
Upgrading a tenant environment to a new version can fail for a number of reasons, such as lack of application dependencies, compilation errors, and duplicate object IDs. When these surface at the end of the flow—for example, when the customer is already down for maintenance—failures are costly both for the customer and for Microsoft. This delays the upgrade process unnecessarily as most of these failures could be found earlier in the flow—for example, when scheduling the update or even when new updates become available.
A new per-tenant extension (PTE) validation service will be created that validates applications on different aspects, such as the following:
- Whether all dependencies have been provided.
- That code compiles both up and downstream (for example, checking that both required symbols are available, and that there are no breaking changes downstream).
- That there are no breaking schema changes.
- That there are no duplicate IDs.
Initially, validation will be triggered on upgrade, and only proceed if passing validation.