This article describes Microsoft Dynamics NAV Database Conversion from one of the following versions to Microsoft Dynamics NAV 2018:
- Microsoft Dynamics NAV 2013 and NAV 2013 R2
- Microsoft Dynamics NAV 2015 and 2016
- Dynamics NAV 2017 and 2018 (cumulative update)
Converting the Dynamics Navision Database, which is often referred to as the technical upgrade, changes the database so that it works on the latest Dynamics NAV platform. The conversion updates the system tables of an old database to the new schema, and the upgrades of all reports to support Report Viewer 2015. It offers you with the latest platform features and performance enhancements.
Preparing the Old Microsoft Dynamics NAV Database
To convert an old database to the MS Dynamics NAV 2018 database, the first task is to back up the old database and then prepare to convert it.
- Create a copy of an old Navision database or create the full database backup.
- Open the development environment that matches the Dynamics Navision version of an old database, and then connect to the old database.
- In the Object Designer, verify all the objects are compiled and no objects are locked. If one or more objects are locked, then the conversion process cannot update the database version number. As a result, the conversion does not complete.
- On the Tools menu, select the Build Server Application Objects, and then select the Yes button.
- If any errors occur, they are displayed in under Error List window. Make sure that you address all the compilation errors before you continue.
- Upload the MS Dynamics Navision 2018 Partner license to the database.
- Run schema synchronization with the validation to synchronize the database schema changes.
- Stop the Dynamics Navision Server instance, and close the development environment.
You can use the Microsoft Dynamics NAV Server Administration tool or the Set-NAVServerInstance cmdlet of the Microsoft Dynamics NAV Administration Shell. To use Set-NAVServerInstance cmdlet, run the following command:
Set-NAVServerInstance –ServerInstance <ServerInstanceName> -Stop
- Clear all the records from the dbo.Server Instance and dbo.Debugger Breakpoint tables in the old database in SQL Server.
Using the SQL Server Management Studio, open and clear the dbo.Server Instance and dbo.Debugger Breakpoint tables of the old database. 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]
- Before you start the given procedure, you can uninstall the old version of MS Dynamics NAV. When you uninstall the Dynamics NAV, the database is still attached to the instance of SQL Server, which you can verify using the SQL Server Management Studio.
Converting the Old Microsoft Dynamics NAV Database
Next, you will convert an old database so that it can be used with the Dynamics NAV 2018.
- If the database is on the Azure SQL Database, include your user account to the dbmanager database role on the master database. This membership is only required for converting the database, and then can be removed afterward.
- Install Microsoft Dynamics NAV 2018. Run the Microsoft Dynamics Navision Setup, and choose to install the Developer option.
- Then Run the MS Dynamics NAV 2018 development environment as an administrator.
- If the development environment is connected to an old database, a dialog box about converting the database will appear. Go to the next step.
- Otherwise, connect to an old NAV database that you prepared in the previous task, and then go to the next step.
- In a dialog box appears, read all the instructions about converting the database carefully because this action cannot be reversed. When you are ready, choose the OK button, and then select the OK button to confirm that you want to convert the database.
Dynamics NAV will now convert the database. This includes an upgrade of the system tables and reports.
- When you are notified that the conversion was successful, choose to the OK.
- If the database references any assemblies that are not added on the Dynamics Navision 2018 installation media (DVD), then add the assemblies to the Add-ins folder on Dynamics NAV Server or the Dynamics NAV Windows client computers.
For the MS Dynamics Navision Windows client, the default path is C:\Program Files (x86)\Microsoft Dynamics NAV\100\RoleTailored Client\Add-ins folder.
For Dynamics NAV Server, the default path is the C:\Program Files\Microsoft Dynamics NAV\110\Service\Add-ins folder.
- Compile all the objects without table schema synchronizing; you will do this later.
- Fix compilation errors.
- Connect Microsoft Dynamics NAV 2018 Server instance to the converted database.
Use the Microsoft Dynamics NAV Server Administration tool or the Set-NAVServerConfiguration cmdlet to connect a Microsoft Dynamics NAV Server instance to the converted Microsoft Dynamics NAV Database.
Example, you can run the following command to recompile all the extensions:
Get-NAVAppInfo -ServerInstance <ServerInstanceName> | Repair-NAVApp
- Run schema synchronization with the validation to complete the database conversion.
- If you converted an MS Dynamics NAV 2016, you will have to modify C/AL code to ensure that the My Settings page works properly in the Microsoft Dynamics NAV Web client.
- Upload the customer license to the converted database.
You have now completed the conversion of the database to be accessed from Microsoft Dynamics Navision 2018. To test the converted the database, you can connect it to MS Dynamics NAV 2018 Server instance that is used by Dynamics NAV clients, and then open a client.