☰ Contents
  Support|  Feedback|  Print|  Share


Upgrade to Business Central


2021/09/11
This topic is for developers and describes the steps required to transfer the data from the old C/AL version (NAV AddOn) to the new AL version (BC Extension) in preparation for an upgrade to Business Central.

Important

The following describes the upgrade of a solution without customizations. If customizations exist in the old solution, the upgrade objects and processes may also need to be customized. Also note that a separate extension must be created for the customizations.

Prerequisites for the Upgrade

  • Minimum NCCR 13.00 Older versions of NCCR must be updated first. Alternatively, the upgrade objects and processes can be customized.

Files for the upgrade

All files needed in each step for the upgrade can be downloaded here: NCCR_UpgradeToBC.zip

Task 1: Rename old tables in the NAV database

The tables of the old solution are already in the NAV database in the 1000000 object range. In order to bring the table structure of the old solution on a uniform basis and to avoid naming conflicts with the tables of the new solution, the old tables must be updated and renamed. To do this, import the NCCR_UpgradeToBC_RenameOldTables.fob file with Replace All. The old tables are then marked with OLD_. The code, variables and functions and all TableRelations to the standard objects were also removed from the old tables.

Task 2: Create new table structure in the NAV database

In the next step, the table structure of the new solution must also be created in the NAV database. To do this, import the NCCR_UpgradeToBC_CreateNewTables.fob file. The tables of the new solution can then be found in the 70000000 object range.

Task 3: Rename old fields in the standard tables of the NAV database and create new fields

The fields of the old solution are already in the standard tables of the NAV database in the 1000000 range. The fields of the new solution are located in the 70000000 range and must also be created in the standard tables. In order to bring the field structure of the old solution on a uniform basis and to avoid naming conflicts with the fields of the new solution, the old fields must be updated and renamed.

Important

The changed standard tables can be found in the file NCCR_UpgradeToBC_RenameOldFields.fob. Import the objects into a separate database, which has no customizations. The objects are based on a Microsoft Dynamics 365 Business Central "Spring 2019" (Version 14.0) AT version.
After you import the objects into a separate database, the fields of the old solution (marked with OLD_NCCR) and the fields of the new solution (marked with NVXGLA) must be copied from the separate database to the NAV database.

The following fields must be copied:

Table 36 Sales Header
  • Field No. 1011900 to Field No. 1011936
  • Field No. 70167825 to Field No. 70167827
Table 112 Sales Invoice Header
  • Field No. 1011900 to Field No. 1011936
  • Field No. 70167825 to Field No. 70167830
Table 114 Sales Cr.Memo Header
  • Field No. 1011900 to Field No. 1011936
  • Field No. 70167825 to Field No. 70167830
Table 289 Payment Method
  • Field No. 1011900 to Field No. 1011901
  • Field No. 70167825
Table 290 VAT Amount Line
  • Field No. 1011900
Table 5900 Service Header
  • Field No. 1011900 to Field No. 1011907
  • Field No. 70167825 to Field No. 70167827
Table 5992 Service Invoice Header
  • Field No. 1011900 to Field No. 1011920
  • Field No. 70167825 to Field No. 70167830
Table 5994 Service Cr.Memo Header
  • Field No. 1011900 to Field No. 1011920
  • Field No. 70167825 to Field No. 70167830

Task 4: Transfer data

The last step is to transfer the data from the tables and fields of the old solution to the tables and fields or table structure of the new solution. To do this, import the NCCR_UpgradeToBC.fob file and then run the NCCR_UpgradeToBC codeunit.

Note

  • The codeunit only needs to be started in one company and runs automatically across all companies in the database.
  • If it is necessary, the codeunit can also be called several times. The data of the old tables and fields will not be deleted. The data of the new tables and fields will be created each time.
☰ Contents
Next Topic: Release Notes
  Support|  Feedback|  Print|  Share
DE|EN Imprint
<>