Preparation 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 NCP_UpgradeToBC_Step1_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.
Preparation 2: Rename old fields in the standard tables of the NAV database
The fields of the old solution are already in the standard tables of the NAV database in the 1000000 range.
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.
The changed standard tables can be found in the file NCP_UpgradeToBC_Step2_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_NCP) must be copied from the separate database to the NAV database.
Once the upgrade is complete, the data from the old NCP Payments system can be prepared for transfer to the new version.
Since the new version is split into 3 apps, 3 separate transfers must also be made.
It is important that first the Payments Base transfer is performed and only then the Payments Export/Import transfers.
First install the 3 apps (also included in the NCP_UpgradeToBC_20220729.zip):
NAVAX Consulting GmbH_NCP Payments Base by NAVAX_188.8.131.52.app
NAVAX Consulting GmbH_NCPE Payments Export by NAVAX_184.108.40.206.app
NAVAX Consulting GmbH_NCPI Payments Import by NAVAX_220.127.116.11.app
These apps contain only the data structure and no application code.
After the installation, the Payments Base upgrade routine can be started via the NCP Upgrade page, which can be found via the search.
After that, the Payments Export and Payments Import upgrade routines can be started via the NCPE Upgrade and NCPI Upgrade page, which can be found via the search.
The upgrade routines only need to be started in one company and run automatically across all companies in the database.
The NCP Payments data is now prepared for the new version.
The last step is to publish the latest version of NCP Payments (consisting of 3 apps) and install it using the Start-NAVAppDataUpgrade command.
The two apps "NCP Customization 18.104.22.168" and "NCP Customization 22.214.171.124" must then be uninstalled and unpublished. The same applies to the 3 apps "NCP Payments Base by NAVAX 126.96.36.199", "NCPE Payments Export by NAVAX 188.8.131.52" and "NCPI Payments Import by NAVAX 184.108.40.206".