This article provides an overview on how to perform Microsoft Dynamics NAV Upgradation to 2018. The Microsoft Dynamics NAV Upgradation process depends on different factors, such as the version of Dynamics NAV that you are upgrading from, and the degree to which your solution differs from the standard version of Dynamics NAV. The main tasks range from converting the database to upgrading application code and data.
Considerations for Microsoft Dynamics NAV Upgradation
Depending on which variant you are upgrading from, and the degree to which your solution differs from the standard version of Dynamics NAV, you may want to prepare your solution for the upgrade.
Names of Variables
Microsoft Dynamics NAV 2018 presents new functions and statements. If your solution includes variables where the name is now used by a standard C/AL function or statement such as REGISTER TABLE CONNECTION or FOR EACH, you must change the variables before you update to Microsoft Dynamics NAV 2018. On the other hand, you can enclose the variable names in quotation marks. If you do not, and you import an object that has this code in text format, you cannot compile the object.
Deprecated or Redesigned Functionality in Microsoft Dynamics NAV Upgradation
If you are going to upgrade a solution that depends on functionality that is deprecated or changed in the default version of Microsoft Dynamics NAV 2018, you must verify that the upgrade code units migrate data correctly.
Upgrade Dynamics NAV Codeunits
When you introduce new changes to the database schema in Microsoft Dynamics NAV 2018, Dynamics NAV will check if these progressions are destructive or not. If the database check shows that the change may lead to data deletion, such as if you are dropping a table column so that the contents of that column will be deleted, this is considered a destructive change. You will be prompted to handle the situation using upgrade Dynamics NAV codeunits.
If a company name includes a special character, an error may show during the upgrade. In this context, special characters include the following:
[ ~ @ # $ % & * ( ) . ! % – + / = ? ]
System Tables with Non-English Names
In the oldest versions of Microsoft Dynamics NAV, you could translate the columns in system tables to a language other than English. Beginning with version 3.0, we advised heavily against this, and versions later than Microsoft Dynamics NAV 2013 R2 require that all columns in all system tables are in English. Accordingly, if you try to open a database with non-English system tables in Microsoft Dynamics NAV 2013 R2 or later, an error popup displays, saying that one or more columns do not exist.
Deprecated Fields and Fields Marked as Obsolete
Sometimes Microsoft will refactor codes so that fields are no longer used, or the functionality is moved from the base application to an extension, for instance. Regularly, the upgrade toolkit will manage the upgrade impact, but for transparency, you can find a list of fields that are deprecated in the current release or marked to be obsolete in a later release.
Automating Upgrade Process
You can utilize Windows PowerShell scripts to help you upgrade to Microsoft Dynamics NAV 2018. You can also use automation to upgrade a single Dynamics NAV database as well as multiple Dynamics NAV databases that use the same application. Microsoft Dynamics NAV 2018 provides sample R scripts that you can adapt for your deployment architecture.
Locus IT has a thorough knowledge of some of the most well-known industries and the particular challenges that exist in this industry. We provide Microsoft Dynamics NAV Upgradation, Dynamics NAV Implementation, Dynamics NAV migration, Dynamics NAV support. For more information please contact us. We’ll be happy to consult with you to refine your current system or create a customized solution.