Upgrading Microsoft System and Base Application to Version 24

Article
04/02/2024

Use this scenario if you have one of the following Business Central versions that use the Microsoft System and Base applications.

2023 release wave 2 (version 23)
2023 release wave 1 (version 22)
2022 release wave 2 (version 21)
2022 release wave 1 (version 20)
2021 release wave 2 (version 19)
2021 release wave 1 (version 18)
2020 release wave 2 (version 17)
2020 release wave 1 (version 16)
2019 release wave 2 (version 15)

Important

See Upgrade Compatibility Matrix to determine which update of version 23 is compatible with your current Business Central version.

The process for upgrading is similar for a single-tenant and multitenant deployment. However, there are some inherent differences. With a single-tenant deployment, the application code and business data are in the same database. In a multitenant deployment, application code is in a separate database (the application database) than the business data (tenant). In the procedures that follow, for a single-tenant deployment, consider references to the application database and tenant database as the same database. Steps are marked as Single-tenant only or Multitenant only where applicable.

Before you begin

Consider known issues

The Known Issues article describes issues that can impact installation, upgrade, and various operations of Business Central on-premises. Review the issues that pertain to the Business Central version you're installing or upgrading to. Some of the issues must be addressed before you upgrade, while others can be resolved afterwards.

Prepare new runtime packages

If a deployment uses extensions that are published as runtime packages, create new versions of runtime packages against the new platform and application. Although you could run Repair-NAVapp on the extensions instead, as described later in this article, this way isn't recommended. Using Repair-NAVapp can lead to problems with the extensions after upgrade.

For more information, see Creating Runtime Packages for Business Central On-Premises.

PowerShell variables used in tasks

Many of the steps in this article use PowerShell cmdlets, which require that you provide values for various parameters. To make it easier for copying or scripting in PowerShell, the steps use the following variables for parameter values. Replace the text between the " " with the correct values for your environment.

$OldBcServerInstance = "The name of the Business Central server instance for your previous version, for example: BC230"
$NewBcServerInstance = "The name of the Business Central server instance for version 24, for example: BC240"
$TenantId = "The ID of the tenant to be upgraded. If not using a multitenant server instance, set the variable to default, or omit -Tenant parameter."
$TenantDatabase = "The name of the Business Central tenant database to be upgraded, for example: Demo Database BC (23-0)" 
$ApplicationDatabase = "The name of the Business Central application database in a multitenant environment, for example: My BC App DB. In a single-tenant deployment, this is the same as the $TenantDatabase" 
$DatabaseServer = "The SQL Server instance that hosts the databases. The value has the format server_name\instance_name, For example: localhost\BCDEMO"
$SystemAppPath = "The file path and name of the System Application extension for the update, for example: C:\DVD\Applications\system application\Source\\Microsoft_System Application.app"
$BusFoundAppPath = "The file path and name of the Business Foundationn extension for the update, for example: C:\DVD\Applications\BusinessFoundation\Source\Microsoft_Business Foundation.app"
$BaseAppPath = "The file path and name of the Base Application extension for the update, for example: C:\DVD\Applications\BaseApp\Source\Microsoft_Base Application.app"
$ApplicationAppPath = "The path and file name to the Application application extension for the update, for example: C:\DVD\Applications\Application\Source\Microsoft_Application.app"
$NewBCVersion = "The version number for the current System, Base, and Application extensions that you'll reinstall, for example: 24.0.24582.0"
$PartnerLicense = "The file path and name of the partner license"
$CustomerLicense = "The file path and name of the customer license"
$AddinsFolder = "The file path to the Add-ins folder of version 24 server installation, for example, C:\Program Files\Microsoft Dynamics 365 Business Central\240\Service\Add-ins."

Task 1: Install version 24

Download the latest available update for Business Central 2024 release wave 1 (version 24) that is compatible with your current version.

For more information, see Dynamics 365 Business Central Upgrade Compatibility Matrix.
Before you install version 24, it can be useful to create a desktop shortcut the Business Central Server Administration tool for the current version. The reason is that the Start menu item for the current version will be replaced with item for the Business Central Server Administration tool for version 24.
Install Business Central version 24 components.

You keep the current version installed to complete some steps in the upgrade process. When you install version 24, you must either specify different port numbers for components (like the Business Central Server instance and web services) or you must stop the current version's Business Central Server instance before you run the installation. Otherwise, you'll get an error that the Business Central Server failed to install.

For more information, see Installing Business Central Using Setup.

Task 2: Upgrade permission sets

Version 18 introduced the capability to define permissions sets as AL objects, instead of as data. Permissions sets as AL objects is now the default and recommended model for permissions. For now, you can choose to use the legacy model, where permissions are defined and stored as data in the database. Whichever model you choose, there are permission set-related tasks you'll have to go through before and during upgrade.

For more information, see Upgrading Permissions Sets and Permissions.

Task 3: Prepare the existing databases

Make backup of the databases.
Disable data encryption.

If the current server instance uses data encryption, disable it. You can enable it again after upgrading.

For more information, see Managing Encryption and Encryption Keys.

Instead of disabling encryption, you can export the current encryption key, which you'll then import after upgrade. However, we recommend disabling encryption before upgrading.
Start Business Central Administration Shell for your current version as an administrator.

For more information, see Run Business Central Administration Shell.
(Single-tenant only) Uninstall all extensions from the old tenants.

In this step, you uninstall the Base Application, System Application (if used), and any other extensions that are currently installed on the database.
1. Get a list of installed extensions.
  
  This step is optional, but it can be useful to the names and versions of the extensions.
  
  To get a list of installed extensions, use the Get-NAVAppInfo cmdlet.
```
Get-NAVAppInfo -ServerInstance $OldBcServerInstance -Tenant $TenantId
```
  For a single-tenant deployment, set the $TenantId to default.
2. Uninstall the extensions.
  
  To uninstall an extension, you use the Uninstall-NAVApp cmdlet.
```
Uninstall-NAVApp -ServerInstance $OldBcServerInstance -Name <extensions name> -Tenant $TenantId -Version <extension version> -Force
```
  Replace <extension name> and <extension version> with the exact name and version the published System Application.
  
  For example, together with the Get-NAVApp cmdlet, you can uninstall all extensions with a single command:
```
Get-NAVAppInfo -ServerInstance $OldBcServerInstance -Tenant $TenantId| % { Uninstall-NAVApp -ServerInstance $OldBcServerInstance -Tenant $TenantId -Name $_.Name -Version $_.Version -Force}
```

Unpublish all system symbols.

To unpublish symbols, use the Unpublish-NAVAPP cmdlet with the -SymbolsOnly switch.

Get-NAVAppInfo -ServerInstance $OldBcServerInstance -SymbolsOnly | % { Unpublish-NAVApp -ServerInstance $OldBcServerInstance -Name $_.Name -Version $_.Version }

What are symbols?

(Multitenant only) Dismount the tenants from the application server instance.

To dismount a tenant, use the Dismount-NAVTenant cmdlet:
```
Dismount-NAVTenant -ServerInstance $OldBcServerInstance -Tenant $TenantId
```

Stop the server instance.

Stop-NAVServerInstance -ServerInstance $OldBcServerInstance

Clear references to .flf license, if used by the database.

A .bclicense license type was introduced in 17.12, 18.7, 19.1. Starting in 2023 release wave 1 (v22), the .flf license type can no longer be used. If your database is using an .flf, you must delete all references to the .flf file in the database. Otherwise, you'll have problems trying to complete the upgrade process.

To delete references to the .flf file, run the following query on the database, for example, by using SQL Server Management Studio:
```
UPDATE [master].[dbo].[$ndo$srvproperty] SET [license] = null
UPDATE [<app database name>].[dbo].[$ndo$dbproperty] SET [license] = null
UPDATE [<tenant database name>].[dbo].[$ndo$tenantproperty] SET [license] = null
```
Replace <app database name> and <tenant database name> with the name of your application and tenant databases, respectively. With a single-tenant deployment, these values are the same.

Learn more about how to query a database

Task 4: Convert application database to version 24

This task runs a technical upgrade on the application database to convert it to the version 23 platform. The conversion updates the system tables of the database to the new schema (data structure). It provides the latest platform features and performance enhancements. The conversion adds the system symbols for the version to the database, so you don't have to manually publish the Systems extension, as you had to do with early releases.

Start Business Central Administration Shell for version 24 as an administrator.

Run the Invoke-NAVApplicationDatabaseConversion cmdlet to start the conversion:

Invoke-NAVApplicationDatabaseConversion -DatabaseServer $DatabaseServer -DatabaseName $ApplicationDatabase

When completed, a message like the following displays in the console:

DatabaseServer      : .\BCDEMO
DatabaseName        : Demo Database BC (23-0)
DatabaseCredentials :
DatabaseLocation    :
Collation           :

Note

When the database is on Azure SQL Database, you may get the following error:

SQL Server: Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated.

If you do, scale up the database resources in Azure SQL, then run the Invoke-NAVApplicationDatabaseConversion cmdlet again. If the conversion is successful, you can then scale it back down to its original setting and continue the upgrade.

Task 5: Configure version 24 server

When you installed version 24 in Task 1, a version 24 Business Central Server instance was created. In this task, you change server configuration settings that are required to complete the upgrade. Some of the changes are only required for upgrade and can be reverted after you complete the upgrade.

Set the server instance to connect to the application database.
```
Set-NAVServerConfiguration -ServerInstance $NewBcServerInstance -KeyName DatabaseName -KeyValue $ApplicationDatabase
```
In a single tenant deployment, this command will mount the tenant automatically. For more information, see Connecting a Server Instance to a Database.
Disable task scheduler on the server instance for purposes of upgrade.
```
Set-NavServerConfiguration -ServerInstance $NewBcServerInstance -KeyName "EnableTaskScheduler" -KeyValue false
```
Be sure to re-enable task scheduler after upgrade if needed.

Restart the server instance.

Restart-NAVServerInstance -ServerInstance $NewBcServerInstance

Task 6: Import version 24 license

Use the Import-NAVServerLicense to upload the version 23 license to the database.

Import-NAVServerLicense -ServerInstance $NewBcServerInstance -LicenseFile $PartnerLicense

Restart the server instance.

Restart-NAVServerInstance -ServerInstance $NewBcServerInstance

Task 7: Synchronize tenant

Synchronize the tenant database with the platform changes in the application database to get it ready for the new extension versions. If you have a multitenant deployment, do these steps for each tenant.

(Multitenant only) Mount the tenant to the version 24 server instance.

To mount the tenant, use the Mount-NAVTenant cmdlet:
```
Mount-NAVTenant -ServerInstance $NewBcServerInstance -DatabaseName $TenantDatabase -DatabaseServer $DatabaseServer -Tenant $TenantId -AllowAppDatabaseWrite
```
Important

You must use the same tenant ID for the tenant that was used in the old deployment; otherwise you'll get an error when mounting or syncing the tenant. If you want to use a different ID for the tenant, you can either use the -AlternateId parameter now or after upgrading, dismount the tenant, then mount it again using the new ID and the OverwriteTenantIdInDatabase parameter.

For upgrade, set the -AllowAppDatabaseWrite parameter. After upgrade, you can dismount and mount the tenant again without the parameter if needed.

At this stage, the tenant state is OperationalWithSyncPending.
Synchronize the tenant with the application database.

Use the Sync-NAVTenant cmdlet:
```
Sync-NAVTenant -ServerInstance $NewBcServerInstance -Mode Sync -Tenant $TenantId
```
With a single-tenant deployment, you can omit the -Tenant parameter and value.

Task 8: Publish extensions

In this task, you'll publish the extensions. As minimum, you publish the new base application and system application extensions from the installation media (DVD). You also publish new versions of any Microsoft extensions and third-party extensions that were used on your old deployment.

Publishing an extension adds the extension to the application database that is mounted on the server instance. Once published, it's available for installing on tenants. This task updates internal tables, compiles the components of the extension behind-the-scenes, and builds the necessary metadata objects that are used at runtime.

The steps in this task continue to use the Business Central Administration Shell for version 24 that you started in the previous task.

Publish the System Application extension (Microsoft_System Application.app).

You find the (Microsoft_System Application.app in the Applications\System Application\Source folder of installation media (DVD).
```
Publish-NAVApp -ServerInstance $NewBcServerInstance -Path $SystemAppPath
```
What is the System Application?
Publish the Business Foundation extension (Microsoft_Business Foundation.app).

You find the Microsoft_Business Foundation.app in the Applications\BusinessFoundation\Source folder of installation media (DVD).
```
Publish-NAVApp -ServerInstance $NewBcServerInstance -Path $BusFoundAppPath
```
Publish the Business Central base application extension (Microsoft_Base Application.app).

The Base Application extension contains the application business objects. You find the (Microsoft_Base Application.app in the Applications\BaseApp\Source folder of installation media (DVD).
```
Publish-NAVApp -ServerInstance $NewBcServerInstance -Path $BaseAppPath
```
Publish the Microsoft_Application extension.

For more information about this extension, see The Microsoft_Application.app File.
```
Publish-NAVApp -ServerInstance $NewBcServerInstance -Path $ApplicationAppPath
```
Publish the new versions of Microsoft extensions.

In this step, you publish new versions of Microsoft extensions that were used on your old deployment. You find the extensions in the Applications folder of the installation media (DVD).
```
Publish-NAVApp -ServerInstance $NewBcServerInstance -Path "<path to Microsoft extension>"
```
For example:
```
Publish-NAVApp -ServerInstance BC230 -Path "C:\W1DVD\Applications\ReportLayouts\Source\Microsoft__Exclude_ReportLayouts.app"
```
Note

A new extension for report layouts, called _Exclude_ReportLayouts, was added in version 20. If you're coming from a version earlier than version 20, make sure to publish and install this extension to get the latest report layout features described at Get Started Creating Report Layouts.
Publish new versions of non-Microsoft extensions. Be sure to include new extensions that contain custom permission sets as AL objects.

If you have new versions of these extensions, built on the Business Central version 24, then publish the new versions.
```
Publish-NAVApp -ServerInstance $NewBcServerInstance -Path "<path to extension>"
```
Recompile extensions not built on version 24.

Important

Don't do this step on extensions published as runtime packages. Create new versions of the runtime packages instead. For more information, see Creating Runtime Packages for Business Central On-Premises.

Do this step for any published extension versions that aren't built on version 24, and you want to reinstall on tenants. These extensions must be recompiled to work with version 24. To recompile the extensions, use the Repair-NAVApp cmdlet:
```
Repair-NAVApp -ServerInstance $NewBcServerInstance -Name <extension name> -Version <extension name>
```
For example, to recompile all extensions that aren't published by Microsoft, you could run the following command:
```
Get-NAVAppInfo -ServerInstance $NewBcServerInstance | Where-Object {$_.Publisher -notlike 'Microsoft'} | Repair-NAVApp
```
Restart the Business Central Server when completed.

Task 9: Synchronize tenant with extensions

Synchronize the tenant's database schema with any schema changes in the new extension versions. If you have a multitenant deployment, do these steps for each tenant.

Synchronize the tenant with the System Application extension.

Use the Sync-NAVApp cmdlet:
```
Sync-NAVApp -ServerInstance $NewBcServerInstance -Tenant $TenantId -Name "System Application" -Version $NewBCVersion
```
Replace $NewBCVersion with the exact version of the published System Application. To get the version, you can use the Get-NAVAppInfo cmdlet.
Synchronize the tenant with the Business Foundation extension.
```
Sync-NAVApp -ServerInstance $NewBcServerInstance -Tenant $TenantId -Name "Business Foundation" -Version $NewBCVersion
```
Replace $NewBCVersion with the exact version of the published Base Application.
Synchronize the tenant with the Business Central Base Application extension.
```
Sync-NAVApp -ServerInstance $NewBcServerInstance -Tenant $TenantId -Name "Base Application" -Version $NewBCVersion
```
Replace $NewBCVersion with the exact version of the published Base Application.

Important

If you're upgrading a Czech (CZ) language version, you must use the -Mode ForceSync parameter to force synchronize the base application; otherwise, synchronization errors occur. For more information, go to Removed table fields in base application cause sync errors.

Synchronize the tenant with the Application extension.

Sync-NAVApp -ServerInstance $NewBcServerInstance -Tenant $TenantId -Name "Application" -Version $NewBCVersion

Synchronize the tenant with Microsoft and non-Microsoft extensions.

For each extension, run the Sync-NAVApp cmdlet:

Sync-NAVApp -ServerInstance $NewBcServerInstance -Tenant $TenantId -Name "<extension name>" -Version <extension version>

Task 10: Upgrade data

In this task, you run a data upgrade for extensions.

Single tenant

Run the data upgrade/installation on extensions in order of dependency: System Application, Business Foundation, Base Application, Application.

Run the data upgrade for the System Application.

To run the data upgrade, use the Start-NAVAppDataUpgrade cmdlet cmdlet:
```
Start-NAVAppDataUpgrade -ServerInstance $NewBcServerInstance -Name "System Application" -Version $NewBCVersion
```
This step will automatically install the new system application on the tenant.
Install the Business Foundation extension. The Base Application has a dependency on this app, so it must be installed before you can upgrade the Base Application.

To install the Business Foundation extension, use the Install-NAVApp cmdlet cmdlet:
```
Install-NAVApp -ServerInstance $NewBcServerInstance -Name "Business Foundation" -Version $NewBCVersion
```

Run the data upgrade for the Base Application, followed by Application extension.

Start-NAVAppDataUpgrade -ServerInstance $NewBcServerInstance -Name "Base Application" -Version $NewBCVersion

Start-NAVAppDataUpgrade -ServerInstance $NewBcServerInstance -Name "Application" -Version $NewBCVersion

This step will automatically install the new versions of these extesnions on the tenant.

Upgrade the new versions of Microsoft extensions and non-Microsoft extensions.

Upgrade any Microsoft and third-party extension that are used in the old deployment to new versions found on the installation media. The new versions are in the Application folder of the DVD. There's a folder for each extension. The extension package (.app file) is in the Source folder.

For each extension, run Start-NAVAppDataUpgrade cmdlet. First, run the data upgrade for the Application extension, then run it for other Microsoft extensions and third-party extensions.

This step will also automatically install the new extension version on the tenant.

Multitenant

On each tenant, run the Start-NavDataUpgrade cmdlet as follows:

Start-NAVDataUpgrade -ServerInstance $NewBcServerInstance -Tenant $TenantId -FunctionExecutionMode Serial -SkipAppVersionCheck

This command will upgrade and install the extensions on the tenant.

Task 11: Install new Microsoft or reinstall 3rd-party extensions

Complete this task to install new first-time Microsoft extensions that you may have published in task 8 or any non-Microsoft extensions for which a new version wasn't published. For example, you would do this step for the _Exclude_ReportLayouts extension if you're upgrading from version 19 or earlier. For each extension, run the Install-NAVApp cmdlet:

Install-NAVApp -ServerInstance $NewBcServerInstance -Name <extension name> -Version <extension version>

Task 12: Upgrade control add-ins

The Business Central Server installation includes new versions of the Microsoft-provided Javascript-based control add-ins, like Microsoft.Dynamics.Nav.Client.BusinessChart, Microsoft.Dynamics.Nav.Client.VideoPlayer, and more. If your solution uses any of these control add-ins, upgrade them to the latest version.

To upgrade the control add-ins from the client, do the following steps:

Open the Business Central client.
Search for and open the Control Add-ins page.
Choose Actions > Control Add-in Resource > Import.
Locate and select the .zip file for the control add-in and choose Open.

The .zip files are located in the Add-ins folder of the Business Central Server installation. There's a subfolder for each add-in. For example, the path to the Business Chart control add-in is C:\Program Files\Microsoft Dynamics 365 Business Central\190\Service\Add-ins\BusinessChart\Microsoft.Dynamics.Nav.Client.BusinessChart.zip.
After you've imported all the new control add-in versions, restart Business Central Server instance.

Alternatively, you can use the Set-NAVAddin cmdlet of the Business Central Administration Shell. For example, the following commands update the control add-ins installed by default. Modify the commands to suit:

Set-NAVAddIn -ServerInstance $NewBcServerInstance -AddinName 'Microsoft.Dynamics.Nav.Client.BusinessChart' -PublicKeyToken 31bf3856ad364e35 -ResourceFile ($AppName = Join-Path $AddinsFolder 'BusinessChart\Microsoft.Dynamics.Nav.Client.BusinessChart.zip')
Set-NAVAddIn -ServerInstance $NewBcServerInstance -AddinName 'Microsoft.Dynamics.Nav.Client.FlowIntegration' -PublicKeyToken 31bf3856ad364e35 -ResourceFile ($AppName = Join-Path $AddinsFolder 'FlowIntegration\Microsoft.Dynamics.Nav.Client.FlowIntegration.zip')
Set-NAVAddIn -ServerInstance $NewBcServerInstance -AddinName 'Microsoft.Dynamics.Nav.Client.OAuthIntegration' -PublicKeyToken 31bf3856ad364e35 -ResourceFile ($AppName = Join-Path $AddinsFolder 'OAuthIntegration\Microsoft.Dynamics.Nav.Client.OAuthIntegration.zip')
Set-NAVAddIn -ServerInstance $NewBcServerInstance -AddinName 'Microsoft.Dynamics.Nav.Client.PageReady' -PublicKeyToken 31bf3856ad364e35 -ResourceFile ($AppName = Join-Path $AddinsFolder 'PageReady\Microsoft.Dynamics.Nav.Client.PageReady.zip')
Set-NAVAddIn -ServerInstance $NewBcServerInstance -AddinName 'Microsoft.Dynamics.Nav.Client.PowerBIManagement' -PublicKeyToken 31bf3856ad364e35 -ResourceFile ($AppName = Join-Path $AddinsFolder 'PowerBIManagement\Microsoft.Dynamics.Nav.Client.PowerBIManagement.zip')
Set-NAVAddIn -ServerInstance $NewBcServerInstance -AddinName 'Microsoft.Dynamics.Nav.Client.RoleCenterSelector' -PublicKeyToken 31bf3856ad364e35 -ResourceFile ($AppName = Join-Path $AddinsFolder 'RoleCenterSelector\Microsoft.Dynamics.Nav.Client.RoleCenterSelector.zip')
Set-NAVAddIn -ServerInstance $NewBcServerInstance -AddinName 'Microsoft.Dynamics.Nav.Client.SatisfactionSurvey' -PublicKeyToken 31bf3856ad364e35 -ResourceFile ($AppName = Join-Path $AddinsFolder 'SatisfactionSurvey\Microsoft.Dynamics.Nav.Client.SatisfactionSurvey.zip')
Set-NAVAddIn -ServerInstance $NewBcServerInstance -AddinName 'Microsoft.Dynamics.Nav.Client.VideoPlayer' -PublicKeyToken 31bf3856ad364e35 -ResourceFile ($AppName = Join-Path $AddinsFolder 'VideoPlayer\Microsoft.Dynamics.Nav.Client.VideoPlayer.zip')
Set-NAVAddIn -ServerInstance $NewBcServerInstance -AddinName 'Microsoft.Dynamics.Nav.Client.WebPageViewer' -PublicKeyToken 31bf3856ad364e35 -ResourceFile ($AppName = Join-Path $AddinsFolder 'WebPageViewer\Microsoft.Dynamics.Nav.Client.WebPageViewer.zip')
Set-NAVAddIn -ServerInstance $NewBcServerInstance -AddinName 'Microsoft.Dynamics.Nav.Client.WelcomeWizard' -PublicKeyToken 31bf3856ad364e35 -ResourceFile ($AppName = Join-Path $AddinsFolder 'WelcomeWizard\Microsoft.Dynamics.Nav.Client.WelcomeWizard.zip')

Task 13: Install upgraded permissions sets

In this task, you install the custom permission sets that you upgraded earlier in this procedure. The steps depend on whether you've decided to use permission sets as AL objects or as data.

For permission sets as AL objects

Publish the extension or extensions that include the permission sets.
Sync the extensions with the tenant.
Install the extensions on the tenant.

For permission sets as data in XML

Set the UserPermissionSetsFromExtensions setting of the Business Central Server instance to false.

Set-NavServerConfiguration -ServerInstance $NewBcServerInstance -KeyName "UsePermissionSetsFromExtensions" -KeyValue false

Restart the serve instance.
Open the Business Central Web client.
Search for and open the Permission Sets page.
Select Import Permission Sets, and follow the instructions to import the XML file.

For more information, see To export and import a permission set.

Task 14: Change application version

After you upgrade your application, we recommend changing the value of application build number that's stored in the database and shown on the Help and Support page to match the new current version. This version isn't updated automatically when you upgrade. If you want the version to reflect the version of the update or your own version, you change it manually. This task serves two purposes. It ensures that personalization works as expected after upgrade. It's also useful for support purposes and answering a common question about the application version.

For more information about version numbers, see Version numbers in Business Central.

Change the application version in the database

Run the Set-NAVApplication cmdlet:

Set-NAVApplication -ServerInstance $NewBcServerInstance -ApplicationVersion $NewBCVersion -Force

For example:

Set-NAVApplication -ServerInstance BC210 -ApplicationVersion 21.0.38071.0 -Force

Run the Sync-NAVTenant cmdlet to synchronize the tenant with the application database.
```
Sync-NAVTenant -ServerInstance $NewBcServerInstance -Mode Sync -Tenant $TenantId
```
With a single-tenant deployment, you can omit the -Tenant parameter and value.
Run the Start-NavDataUpgrade cmdlet to change the version number:
```
Start-NAVDataUpgrade -ServerInstance $NewBcServerInstance -FunctionExecutionMode Serial -Tenant $TenantId
```
The data upgrade process will be running in the background after running the above Start-NAVDataUpgrade cmdlet. You check on the progress using the Get-NAVDataUpgrade cmdlet: such as: Get-NAVDataUpgrade -ServerInstance $NewBcServerInstance -Tenant $TenantId -Progress or Get-NAVDataUpgrade -ServerInstance $NewBcServerInstance -Tenant $TenantId -Detailed.

Don't stop the Business Central Server instance until the process is complete, that is, when you see State = Completed in the results from the Get-NAVDataUpgrade cmdlet. Also, you can't do operations like installing extensions until the state is operational. It can take several minutes before the process completes.

Change the application version shown on the Help and Support page in the client

The Business Central Server includes a configuration setting called Solution Version Extension (SolutionVersionExtension). This setting lets you specify an extension whose version number will show as the Application Version on the client's Help and Support page. Typically, you'd use the extension considered to be your solution's base application. You set Solution Version Extension to ID of the extension. For example, if your solution uses the Microsoft Base Application, set the value to 437dbf0e-84ff-417a-965d-ed2bb9650972.

You can set Solution Version Extension by using the Business Central Server Administration tool or the Set-NAVServerConfiguration cmdlet of the Business Central Administration Shell.

The following example uses the Set-NAVServerConfiguration cmdlet to set the Solution Version Extension to the Microsoft Base Application:

Set-NAVServerConfiguration -ServerInstance $NewBcServerInstance -KeyName SolutionVersionExtension -KeyValue "437dbf0e-84ff-417a-965d-ed2bb9650972" -ApplyTo All

Post-upgrade tasks

IMPORTANT If you have a two- or three-tiered deployment and the Business Central Web Server and Business Central Server are on different computers, reconfigure delegation according to Configuring Delegation for Business Central Web Server.
Enable task scheduler on the server instance.
(Multitenant only) For tenants other than the tenant that you use for administration purposes, if you mounted the tenants using the -AllowAppDatabaseWrite parameter, dismount the tenants, then mount them again without using the -AllowAppDatabaseWrite parameter.
If you want to use data encryption as before, enable it.

For more information, see Managing Encryption and Encryption Keys.

Optionally, if you exported the encryption key instead of disabling encryption earlier, import the encryption key file to enable encryption.
Import the customer license

Import the customer license by using the Import-NAVServerLicense cmdlet, as you did with the partner license. You'll have to restart the server instance afterwards.
```
Import-NAVServerLicense -ServerInstance $NewBcServerInstance -LicenseFile $CustomerLicense
Restart-NAVServerInstance -ServerInstance $NewBcServerInstance
```