Upgrading the Data to Business Central: Single-Tenant Deployment

Artikel
04/18/2024

Note

If you're coming from version 13 or earlier, Business Central Spring 2019 (v14) is a required step to upgrade to the latest version of Business Central. However, mainstream support for version 14 ends in October 2023, and minor updates to the version are no longer available. New customers can't use version 14 in production, but only as a path for upgrading to latest version. Existing customers on version 14 remain supported by Microsoft as defined in the Fixed Lifecycle Policy.
All version 14 updates are compatible with any update version of Business Central 2024 release wave 1 and later release waves.

This article describes the tasks required for upgrading the data of a Dynamics NAV or Business Central database to a Business Central major version or cumulative update.

This article pertains to a single-tenant deployment. For upgrade instructions for a multitenant deployment, see Upgrading the Data: Multitenant Deployment.

About Data Upgrade

You use data conversion tools provided with Business Central to convert the old data with the old version's table and field structure, so that it functions together with the new version's table and field structure. Mainly, only table objects and table data are modified during the data upgrade process. Other objects, such as pages, reports, codeunits, and XMLports are upgraded as part of the application code upgrade process.

The data upgrade process described in this article leads you through the database conversion (technical upgrade) and then the upgrade of the actual data, which is achieved by using the upgrade toolkit/upgrade codeunits.

Prerequisites

Before you start the upgrade tasks, make sure you meet the following prerequisites:

Your computer uses the same codepage as the data that will be upgraded.

If you use conflicting codepages, some characters will not display in captions, and you might not be able to access the upgraded database. This is because Dynamics NAV must remove incorrect metadata characters to complete the data upgrade. In this case, after upgrade, you must open the database in the development environment on a computer with the relevant codepage and compile all objects. This adds the missing characters again.

Optionally, you can export the captions before the upgrade. For more information, see How to: Add Translated Strings for Conflicting Text Encoding Formats.
(Upgrading from Dynamics NAV only) Custom V1 extensions used in the old deployment have been converted to V2 extensions.

For more information, see Converting Extensions V1 to Extensions V2.
You have upgraded the application code, and have the FOB files that contain the upgraded application code.

For more information about upgrading the application code, see Upgrading the Application Code.

You have the upgrade toolkit FOB files that are available on the Business Central installation media (DVD).

The upgrade toolkit includes upgrade codeunits for handling the data upgrade. The upgrade toolkit can be in the same FOB file as the application code or in a separate FOB file.

For W1 versions, you can find the default upgrade toolkit objects in the UpgradeToolKit\Data Conversion Tools folder on the Business Central installation media (DVD). Choose the FOB that matches the Dynamics NAV version from which you are upgrading:

From	To Business Central April 2019	To Business Central October 2018
Microsoft Dynamics NAV 2015	Upgrade80014x.FOB	Upgrade800130.FOB
Microsoft Dynamics NAV 2016	Upgrade90014x.FOB	Upgrade900130.FOB
Microsoft Dynamics NAV 2017	Upgrade100014x.FOB	Upgrade1000130.FOB
Microsoft Dynamics NAV 2018	Upgrade110014x.FOB	Upgrade1100130.FOB
Business Central Fall 2018	Upgrade13x14x.FOB	Not applicable

For local versions, you will find the upgrade toolkit objects in the UpgradeToolKit\Local Objects folder. The files follow the same naming convention except they include the 2-letter local version, such as Upgrade110014x.DK.fob for Denmark, Upgrade110014x.DE.fob for Germany, or Upgrade90014x.IN.fob for India.

You have exported the customized permission sets (except SUPER) and permissions from the old database that you want to reuse in the upgraded database.
- When upgrading from Dynamics NAV
  
  To export permission sets and permissions, you run running XMLPort 9171 and 9172.
  
  It is important that you exclude the SUPER permission set when running XMLPort 9171. You can do this by adding the filter Role ID is <>SUPER.
  
  For more information, see Exporting and Importing Permission Sets and Permissions.
- When upgrading from an earlier version of Business Central
  
  In the client, search for and open the Permission Sets page, select the user-defined permission sets that you want to keep, and then choose Export Permission Sets. This action runs XMLPort 9173 Export Permission Sets.
If the old deployment uses data encryption, you have exported the encryption key file that it used for the data encryption.

For more information, see How to: Export and Import Encryption Keys.
(Optional) Make a copy of the configuration file (web.config or navsettings.json) for all Business Central Web Server instances in the old deployment.
Business Central has been installed.

As a minimum, you must install the following components:
- Server
- SQL Server Components
- Business Central Web Server components
- Dynamics NAV Development Environment(DISCONTINUED AFTER: Business Central Spring 2019).
- AL Development Environment
- (optionally) Business Central Server Administration tool
For more information, see Installing Business Central Using Setup.

Note

If the old Dynamics NAV application uses Payment Services for Microsoft Dynamics ERP, be aware that this was discontinued in Microsoft Dynamics NAV 2017. This means that most of the objects that are associated with this feature will be deleted during the upgrade. Some objects you will have to manually delete.

Task 1: Create full SQL backup of old database

Create a full backup of the old database in the SQL Server. Alternatively, you can make a copy of the old database and perform the upgrade tasks on the copy.

For more information, see Create a Full Database Backup (SQL Server).

Task 2 Uninstall all extensions in old database

Open the Dynamics NAV Administration Shell or Business Central Administration Shell that matches to old database, and run these commands:

To get a list of the extensions that are installed, run this command:
```
Get-NAVAppInfo -ServerInstance <ServerInstanceName> -Tenant default
```
Replace <ServerInstanceName> with the name of the Dynamics NAV Server instance that the database connects to.
For each extension, run this command to uninstall it:
```
Uninstall-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>
```
Replace <ServerInstanceName> with the name of the Dynamics NAV Server instance that the database connects to.

Replace <Name> and <N.N.N.N> with the name and version of the Extension V1 as it appeared in the previous step.

Alternately, to remove them all at once, you can run this command:
```
Get-NAVAppInfo -ServerInstance <ServerInstanceName> -Tenant default | % { Uninstall-NAVApp -ServerInstance <ServerInstanceName> -Name $_.Name -Version $_.Version }
```

Task 3: Upload Business Central partner license to old database

By using the Dynamics NAV Development Environment that matches the old database, upload the Business Central license to the database.

For more information, see Uploading a License File for a Specific Database.

Task 4: Delete all objects except tables in old database

In the development environment version that matches the database, open the old database, open Object Designer, select all objects except tables, and then choose Delete.

You can also use the DeleteObjects command of the finsql.exe.

Task 5: Clear server instance and debugger breakpoint records in old database

Clear all records from the dbo.Server Instance and dbo.Debugger Breakpoint tables in the database in SQL Server.

Make sure that you stop the old server instance, and close any tools that connect to the database, such as the Dynamics NAV Administration Tool and development environment.
Using SQL Server Management Studio, open and clear the dbo.Server Instance and dbo.Debugger Breakpoint tables of the old database. For example, you can run the following SQL query:
```
DELETE FROM [<My NAV Database Name>].[dbo].[Server Instance]
DELETE FROM [<My NAV Database Name>].[dbo].[Debugger Breakpoint]
```

Task 6: Convert old database to Business Central

If the database is on Azure SQL Database, you may get add your user account to the dbmanager database role on the master database.

This membership is only required for converting the database, and can be removed afterwards. This step isn't required for Azure SQL Managed Instance.

To convert the old database to the Business Central format, run the new Dynamics NAV Development Environment for Business Central, open the old database, and follow the conversion instructions.

If you do not run the development environment as an administrator, you will get an error and the conversion will be stopped.

For more information about how to open a database, see Open a Database.

Important

Do not run schema synchronization at this time. Choose to run it later.

Task 7: Import upgraded application objects to converted database

Using Dynamics NAV Development Environment for Business Central, import the application objects that you want in the database. This includes the application objects FOB file (from the application code upgrade) and the upgrade toolkit objects FOB file.

Import the application objects FOB file first, and then import the upgrade toolkit FOB file.

For more information, see Importing Objects.
IMPORTANT When prompted about table synchronization, set the Synchronize Schema option to Later.
When you import the FOB file, if you experience metadata conflicts, the Import Worksheet windows appears.

Review the Worksheet page. For more information, see Import Worksheet.

Choose Replace All, and then OK to continue.

Task 8: Connect a Business Central Server instance to converted database

You use the Business Central Server Administration tool or Set-NAVServerConfiguration cmdlet in the Business Central Administration Shell to connect a Business Central Server instance to the converted database.

The service account that is used by the Business Central Server instance must be a member of the db_owner role in the Business Central database on SQL Server or Azure SQL Database.

For more information, see Connecting a Server Instance to a Database and Giving the account necessary database privileges in SQL Server.

Important

When upgrading a large database, you should increase the SQL Command Timeout setting for the Business Central Server instance, to avoid timeouts during schema synchronization. The default setting is 30 minutes.

Task 9: Compile all objects in converted database

In the Dynamics NAV Development Environment, set it to use the server instance that connects to the database.

For more information, see Changing the Server Instance.
Use the Dynamics NAV Development Environment or finsql.exe to compile all objects. This includes the imported application objects, data tables, and system tables.

Important

Choose to run schema synchronization later. For example, in Object Designer, choose Tools, choose Compile, set the Synchronize Schema option to Later, and then choose OK. For more information, see Compiling Objects.
(Upgrade from Microsoft Dynamics NAV 2016 and earlier only) If you get errors on the following table objects, use the Object Designer to delete the objects because they are no longer used.
- Table 470 Job Queue (replaced by the Task Scheduler)
- Table 824 DO Payment Connection Details
- Table 825 DO Payment Connection Setup
- Table 827 DO Payment Credit Card
- Table 828 DO Payment Credit Card Number
- Table 829 DO Payment Trans. Log Entry
- Table 1510 Notification Template
Important

When you delete a table object, in the Delete confirmation dialog box that appears, set the Synchronize Schema option to Force.

In this step, it's very important that you do not use the Sync. Schema For All Tables option from the Tools menu.
(Upgrade from Microsoft Dynamics NAV 2016 and earlier only) If the old database includes test runner codeunits, you will get errors on these codeunits that the OnBeforeTestRun and OnAfterTestRun trigger signatures are not valid. To fix these issues, you change the signature of the OnBeforeTestRun and OnAfterTestRun triggers to include the TestPermission parameter.

For more information, see Resolving OnBeforeTestRun and OnAfterTestRun Trigger Errors When Converting a Database.

The triggers for codeunit 130400 CAL Test Runner and 130402 CAL Command Line Test Runner will be updated for you during the data upgrade.

Task 10: (Upgrade from Dynamics NAV 2018 or Business Central Fall 2018 only ) Increase the application version of converted database

You must increase the application version that is assigned to the database.

Use the Set-NAVApplication cmdlet of the Business Central Administration Shell to increase the application version number of the database from its current version.

To see the current version, use the following command:

Get-NAVApplication -ServerInstance <ServerInstanceName>

To increase the version by 1, run the following command:

Set-NAVApplication -ServerInstance <ServerInstanceName> -IncrementApplicationVersion

Or, to specify change to another version, run the following command:

Set-NAVApplication -ServerInstance <ServerInstanceName> -ApplicationVersion <N.N.N.N> -Force

For example, if the old version was 11.0.24279.0, then you could change the version to 14.0.24279.0.

Task 11: Run the schema synchronization on converted database

Synchronize the database schema with validation.

For example, run the Sync-NAVTenant cmdlet from the Business Central Administration Shell.

Sync-NAVTenant -ServerInstance <ServerInstanceName>

When completed, the tenant (database) should have the status OperationalDataUpgradePending. To verify this, run the following cmdlet:

Get-NAVTenant -ServerInstance <ServerInstanceName> -tenant default

For more information, see Synchronizing the Tenant Database and Application Database.

Task 12: Run data upgrade on converted database

A data upgrade runs the upgrade toolkit objects, such as upgrade codeunits and upgrade tables, to migrate business data from the old table structure to the new table structure. You can start the data upgrade from the Dynamics NAV Development Environment or Business Central Administration Shell.

Open the Business Central Administration Shell as an administrator, and then run Start-NavDataUpgrade cmdlet as follows:
```
Start-NavDataUpgrade -ServerInstance <ServerInstanceName> -FunctionExecutionMode Serial -ContinueOnError  
```
Replace <ServerInstanceName> with the name of the Business Central Server instance that is connected to the database.

Note

In the last phase of data upgrade, all companies will be initialized by running codeunit 2 Company Initialization. This is done automatically. If you want to skip company initialization, then use the Start-NavDataUpgrade with the -SkipCompanyIntitialization parameter.

To view the progress of the data upgrade, you can run Get-NavDataUpgrade cmdlet with the –Progress switch.

The data upgrade process runs CheckPreconditions and Upgrade functions in the upgrade codeunits. If any of the preconditions are not met or an upgrade function fails, you must correct the error and resume the data upgrade process. If CheckPreconditions and Upgrade functions are executed successfully, codeunit 2 is automatically run to initialize all companies in the database unless you set the -SkipCompanyIntitialization parameter.
Check for and resolve upgrade errors.

Run the following command to get a list of any errors that have occurred:
```
Get-NAVDataUpgrade -ServerInstance <ServerInstanceName> -ErrorOnly
```
Resolve the errors before going to the next task.

Task 13: Upgrade Javascript-based control add-ins to new versions

The Business Central Server installation includes new versions of Microsoft-provided Javascript-based control add-ins, such as the Business Chart control add-in. If you application is using any of these add-ins, you must upgrade them to the new versions as follow:

Open the Business Central client.

If the application uses the Business Chart control add-in, you will get an error about High Charts. Upgrading the Business Chart control add-in will clear this error.
Search for and open the Control Add-ins page.

The page lists all the registered control add-ins.
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 is a sub-folder for each add-in. For example, the path to the Business Chart control add-in is C:\Program Files\Microsoft Dynamics 365 Business Central\140\Service\Add-ins\BusinessChart\Microsoft.Dynamics.Nav.Client.BusinessChart.zip.
After you have imported all the new control add-in versions, restart Web Server instance.

Task 14: Publish and generate symbols for extensions

Complete this task if you are upgrading one of the following:

Microsoft Dynamics NAV 2018 deployment that uses V2 extensions.
Denmark (DK) version of Microsoft Dynamics NAV 2017 or earlier
German (DE) version of Dynamics NAV or Business Central October 2018 (Cumulative Update 2 or earlier)

In this task, you will publish and generate symbols that are required for using V2 extensions. Symbols are the application programming interface between AL code and C/AL code. Symbols enable the ability to reference C/AL objects from AL objects. Symbols are provided as an extension package, and are published to the server instance, but not installed on tenants. There are three types of symbols: system, application, and test. System symbols contained references to the platform system objects. The application symbols contained references to the business application objects. The test symbols contained references to the test libraries used by Microsoft extensions.

To get list of the extensions currently published symbols, run the following command from the Business Central Administration Shell:
```
Get-NAVAppinfo -ServerInstance <ServerInstanceName> -SymbolsOnly
```
Unpublish the existing system, test, and application symbols by using the Unpublish-NAVAPP cmdlet:
```
Unpublish-NAVApp -ServerInstance <ServerInstanceName> -Name <name> -Version <n.n.n.n>
```
Publish the system.app and test.app symbol files.

If you installed the AL Development Environment, you can find the symbol files where your installed the environment, which by default is C:\Program Files (x86)\Microsoft Dynamics 365 Business Central\140. Otherwise, you can find the files in the ModernDev folder on the installation media.

To publish the symbols, open the Business Central Administration Shell as an administrator, and run the following command for each of the symbol files:
```
Publish-NAVApp -ServerInstance <ServerInstanceName> -Path <SymbolFilePath> -PackageType SymbolsOnly
```
Generate the application symbol references by using the finsql.exe file as follows:
1. Make sure that Enable loading application symbol references at server startup (EnableSymbolLoadingAtServerStartup) is set on the Business Central Server instance.
  
  For more information, see Configuring Business Central Server.
2. Open a command prompt as an administrator, change to the directory where the finsql.exe file has been installed as part of Dynamics NAV Development Environment, and then run the following command:
```
finsql.exe Command=generatesymbolreference, Database="<MyDatabaseName>", ServerName=<DatabaseServerName>\<DatabaseInstance>
```
  Replace values for the Database and ServerName settings to suit.
  
  If the application database contains test objects (ID 130000-139999), then make sure to exclude these objects when generating symbols. You can do this by using the -Filter parameter and running the command twice:
```
finsql.exe command=generatesymbolreference, ServerName=<DatabaseServerName>\<DatabaseInstance>, Database="<MyDatabaseName>", filter="Object ID=1..129999"
```
```
finsql.exe command=generatesymbolreference, ServerName=<DatabaseServerName>\<DatabaseInstance>, Database="<MyDatabaseName>", filter="Object ID=140000..1999999999"
```
  Note
  
  This command does not generate a file. It populates the Object Metadata table in the database.
3. When you run the command, the console returns to an empty command prompt, and does not display or provide any indication about the status of the run. However, the finsql.exe may still be running in the background. It can take several minutes for the run to complete, and the symbols will not be generated until such time. You can see whether the finsql.exe is still running by using Task Manager and looking on the Details tab for finsql.exe.
  
  When the process ends, a file named navcommandresult.txt is saved to the Dynamics NAV Client connected to Business Central installation folder. If the command succeeded, the file will contain text like [0] [06/12/17 14:36:17] The command completed successfully in '177' seconds. If the command failed, another file named naverrorlog.txt will be generated. This file contains details about the error(s) that occurred.
For more information about generation symbols, see Running C/SIDE and AL Side-by-Side.
1. Restart the Business Central Server instance.

Task 15: Upgrade or repair V2 extensions

Complete this task if you are upgrading from a Microsoft Dynamics NAV 2018 deployment that uses V2 extensions. In this step, you will upgrade the V2 extensions that you previously uninstalled. The upgrade process will reinstall these extensions.

The Business Central installation media (DVD) includes several new versions of Microsoft extensions (that is, extensions that have Microsoft as the publisher). If your old deployment uses these extensions, you have to upgrade the current versions to the new versions.

To get list of the extensions currently published on the application, run the following command from the Business Central Administration Shell:
```
Get-NAVAppinfo -ServerInstance <ServerInstanceName>
```
Upgrade the Microsoft extensions that were published in the old deployment to new versions.

The new extension versions are found in the \Extensions folder of the installation media (DVD). Follow these steps for each extension by using the Business Central Administration Shell:
1. Publish the new extension version by running the Publish-NAVApp cmdlet:
```
Publish-NAVApp -ServerInstance <ServerInstanceName> -Path <ExtensionFileName> 
```
2. Synchronize the schema with the database by running the Sync-NAVApp cmdlet:
```
Sync-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>
```
3. Upgrade the data of the extensions.
  
  To run the data upgrade, run the Start-NAVAppDataUpgrade cmdlet:
```
Start-NAVAppDataUpgrade -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>
```
  Apart from upgrading the data, this command will install the new extension version.
For more information about publishing extensions, see Publish and Install an Extension.
Repair, synchronize, and install other currently published extension versions that you still want to use, but have not been upgraded to new versions.

For each extension, complete the following steps from the Business Central Administration Shell:
1. Compile the extension to make it work with the new platform by running the Repair-NAVApp cmdlet.
```
Repair-NAVApp -ServerInstance <ServerInstanceName> -Name <Extension Name> -Version <N.N.N.N>
```
2. Synchronize the schema with the database by running the Sync-NAVApp cmdlet:
```
Sync-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>
```
3. Install the extension by running the Install-NAVApp cmdlet:
```
Install-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>
```

(Optional) Unpublish unused extension versions by running the Unpublish-NAVApp:

Unpublish-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>

Task 16: Publish and install local functionality extensions

Complete this task if you are upgrading one of the following:

Denmark (DK) version of Microsoft Dynamics NAV 2017 or earlier
German (DE) version of Dynamics NAV or Business Central October 2018 (Cumulative Update 2 or earlier)
India (IN) version of Dynamics NAV 2016

With these language versions, some of the local functionality has been moved from the base application to extensions. These extensions will have to be published and installed to maintain the functionality. The extensions are avilable on the installation media (DVD).

If you are upgrading from a Denmark (DK) version, you must publish and install the following extensions to get the local functionality:

Name	Extension package
OIOUBL	OIOUBL.app
Payroll Data Import Definitions (DK)	ImportDKPayroll.app
Payment and Reconciliation Formats (DK)	FIK.app
Tax File Formats (DK)	VATReportsDK.app

If you are upgrading from a German (DE) version you must publish and install the following extensions to get the local functionality:

Name	Extension package
ELSTER VAT Localization for Germany	Elster.app

If you are upgrading from an India (IN) version of Dynamics NAV 2016, you must publish and install the following extensions to get the local functionality:

Name	Extension package
India Tax Base	IndiaTaxBase.app
India Tax Engine	IndiaTaxEngine.app
India Tax GST	IndiaTaxGST.app
India Upgrade Tables	IndiaUpgradeTables.app
India TCS	IndiaUPGTCS.app
India TDS	IndiaUPGTDS.app
Fixed Asset Depreciation for India	INFADepreciation.app
India Gate Entry	INGateEntry.app
India Voucher Interface	INVoucherInterface.app
India Data Migration	UPGIndia.app

Follow these steps for each extension by using the Business Central Administration Shell:

Publish the new extension version by running the Publish-NAVApp cmdlet:
```
Publish-NAVApp -ServerInstance <ServerInstanceName> -Path <ExtensionFileName> 
```
The new extension versions are found in the \Extensions folder of the installation media (DVD).

Synchronize the schema with the database by running the Sync-NAVApp cmdlet:

Sync-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>

Install the newly published local functionality extensions by running the Install-NAVApp cmdlet:
```
Install-NAVApp -ServerInstance <ServerInstanceName> -Name <Name> -Version <N.N.N.N>
```

Task 17: Import permission sets and permissions

Import the permission sets and permissions XML files that you exported from the old database as follows:

Upgrade from Dynamics NAV:
1. Open table 2000000004 Permission Sets in the client, and delete all permission sets except SUPER.
  
  Note
  
  You are only required to delete those permission sets that are also included in the permission sets XML file that you will import. Because if you try to import a permission set with the same name as one already in the database, you will get an error.
2. Run XMLport 9171 and XMLport 9172 to import the permission sets and permission XML files.
  
  For more information, see How to: Export and Import Permission Sets and Permissions.
Upgrade from an earlier Business Central version:
1. In the client, search for and open the Permission Sets page.
2. Delete all user-defined permissions.
3. Choose Import Permission Sets, then select the permissions set file that you exported previously.
  
  This action runs the XMLPort 9174 Import Tenant Permissions.

Task 18: (Optional) Import data encryption key

If you want to use data encryption as before, you must import the data encryption key file that was exported previously.

For more information, see Exporting and Importing Encryption Keys.

Task 19: Set the language of customer database

In the Dynamics NAV Development Environment, choose Tools, choose Language, and then select the language of the original customer database.

Task 20: (Optional) Update Web Server instance configuration file

If you have installed the Business Central Web Server, populate the navsettings.json file for the Business Central Web Server instance with the settings of the old web.config file or navsettings.json.

If the old deployment used a web.config file, then you have to manually change the settings in the navsetting.json file that is used on the new Business Central Web Server instance.
If you upgraded from Business Central October 2018, you can replace the navsettings.json file on the new Business Central Web Server instance with the old file. However, as of Business Central April 2019, the following settings are now configured under a root element called ApplicationIdSettings instead of the root element NAVWebSettings.
- AndroidPrivacy
- AndroidSoftwareLicenseTerms
- AndroidThirdPartyNotice
- BaseHelpUrl
- BaseSettingsSectionName
- CommunityLink
- FeedbackLink
- IosPrivacy
- IosSoftwareLicenseTerms
- IosThirdPartyNotice
- KeyboardShortcutsLink
- PrivacyLink
- LegalLink
- SignInHelpLink
If the old navsettings.json file uses any of these settings, then you will have to move them from the NAVWebSettings element to the ApplicationIdSettings element.

For more information about the navsettings.json file, see Configuring Business Central Web Server Instances.

(Optional) Task 21: Delete upgrade objects

At this point, you have upgraded the database to Business Central. Now, you can delete the upgrade codeunits and upgrade table objects that you imported in task 9. This task is recommended but not required.

When you delete tables, on the Delete dialog box, set the Synchronize Schema option to Force.

Del via