topic hubPlatform, DevOps & Performanceofficial - Microsoftreviewed - checked by Opus

Business Central 2023 release wave 1

Upgrade documentation for Business Central on-premises 2023 release wave 1 (version 22). It covers upgrade paths from version 14 and versions 15-21, technical and application upgrade steps, C/AL to AL conversion, table migration between extensions, permissions, reports, and the compatibility matrix.

Path: Business Central on-premises > Upgrade > Earlier versions > Business Central 2023 release wave 1 · tier official · system platform · narrative reviewed (checked by Opus)

Overview

This section is the upgrade guide for Business Central 2023 release wave 1 (version 22) on-premises. It starts with general considerations and an overview page that lists upgrade paths, deprecated features, and the move to online. From there the pages split by starting point: from version 14 (C/AL), or from versions 15-21.

For version 14, there are separate routes for an unmodified C/AL application and for a customized one. Both replace the base application with the Microsoft System and Base Application extensions. Customized solutions need code conversion with Txt2Al and data moved with migration.json and the DestinationAppsForMigration setting. A separate page covers the technical upgrade from version 14 to 22, which converts C/AL customizations to an AL base application extension. For versions 20 and 21 there is a technical upgrade page, and another page covers installing a version 22 update.

Supporting pages cover moving tables and fields between extensions (up or down the dependency graph), upgrading permission sets to AL objects, and report platform changes from version 20. Start with the overview page and the compatibility matrix, then pick the path that matches your current version.

Key points

  • Version 22 is 2023 release wave 1. Upgrade guidance covers sources from version 14 and versions 15-21.
  • The compatibility matrix gives minimum update versions for upgrades between major versions. For later upgrades, it also notes that sources at version 24 or earlier must target version 25 first.
  • Customized version 14 C/AL solutions are converted to AL with the Txt2Al tool, then data is migrated using DestinationAppsForMigration and migration.json.
  • Unmodified version 14 applications are upgraded by replacing the base application with System and Base Application extensions.
  • Technical upgrade steps include database conversion, extension recompilation, tenant mounting and synchronization, permission set upgrade, and add-in copying.
  • Moving table ownership between extensions uses migration.json. Moving up the dependency graph needs a two-stage process with a transition extension.
  • Permissions move from legacy data-based permissions to AL object-based Permission Set and Permission Set Extension objects.
  • Report upgrade guidance for version 20 and later covers the new rendering model, event changes, and Word and custom layouts.

Learn pages

Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.

What Learn documents here 8 of 15 Learn pages

Show 7 more