Share This Post

NAV Updates

Dynamics NAV Upgrade Procedure

Microsoft Dynamics NAV Upgrade

This topic provides an overview of the Dynamics NAV Upgrade. The upgrade process depends on another factor, such as the version of the MS Dynamics Navision that you are upgrading from, and the degree to which your solution differs from the standard version of the Dynamics NAV. The mains tasks range from converting the database to upgrading the application code and information.

Dynamics NAV Upgrade

Dynamics NAV Upgrade

Use the below table to determine the procedures that you must complete for your upgrade.

Scenario Procedures
 Full Dynamics Navision upgrade from one of the   following versions:

  • Microsoft Dynamics NAV 2015
  • Microsoft Dynamics NAV 2016
  • Microsoft Dynamics NAV 2017
  1. Upgrade the Application Code
  2. Upgrade the Data
 A full upgrade from one of the   following versions:

  • Microsoft Dynamics NAV 2013
  • Microsoft Dynamics NAV 2013 R2
  1. Microsoft Dynamics NAV upgrade Cumulative Update 2:
    1. Download Microsoft Dynamics NAV 2018 CU2.
    2. Upgrade the Application Code
    3. Upgrade the Data
  2. Upgrade to the latest Microsoft Dynamics Navision 2018 cumulative update (CU):
    1. Upgrade the Application Code
    2. Upgrade the Data
 A full upgrade from one of the following versions:

  • Microsoft Dynamics NAV 2009 SP1
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 5.0
  • Microsoft Dynamics NAV 4.0
  1. Upgrade to Microsoft Dynamics NAV 2013.
    For more data, see Upgrading to the Microsoft Dynamics NAV 2013 in the MSDN Library. Alternatively, you can upgrade from the Microsoft Dynamics Navion 2009 SP1 or Microsoft Dynamics Navision 2009 R2 to Dynamics NAV 2015 as described on the Dynamics NAV.
  2. Upgrade to the Dynamics NAV 2018 Cumulative Update 2.
    1. Download Microsoft Dynamics NAV 2018 CU2.
    2. Upgrade the Application Code
    3. Upgrade the Data
  3.  Dynamics NAV upgrades to the latest Microsoft Dynamics NAV 2018 cumulative update (CU) by following steps a and b above.

After the Dynamics NAV upgrade, links between interaction records and logged email messages are lost. To resolve this issue, the administrator has to log all emails again to restore the links.

 Technical upgrade of the Microsoft Dynamics NAV 2018 database to the new platform version with no app changes, such as with the cumulative update
  • Converting a Database

You can also use this procedure to convert the previous MS Dynamics Navision database to the Dynamics NAV technical requirements, and then upgrade the app and information later.

Before you begin the upgrade process, see the Upgrade Considerations for the tips about things to consider when you prepare to upgrade to MS Dynamics NAV 2018.

Automating the Upgrade Method using Sample Windows PowerShell Scripts

You can use the Windows PowerShell scripts to help you Dynamics NAV upgrade to Microsoft Dynamics NAV. You can use the automation to upgrade the single Dynamics NAV database as well as the multiple NAV databases that use the same application. Microsoft Dynamics NAV 2018 offers the sample scripts, you can adapt for your deployment architecture.

Considerations for Upgrading Dynamics NAV

Depending on which version you are upgrading from, and the degree to which your solution differs from the standard version of the MS Dynamics NAV, you may wish to prepare your solution for the Dynamics NAV upgrade. This topic gives the tips for things to consider when you prepare to upgrade to Dynamics NAV 2018.

Names of Variables

Microsoft Dynamics NAV 2018 introduces new functions and statements. If your solution involves the variables where the name is used by the standard C/AL function such as REGISTERTABLECONNECTION, you must change the variables before you upgrade to Microsoft Dynamics NAV 2018. You can enclose the variable names in the 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

If you are upgrading the solution which depends on the functionality that is deprecated or changed in the default version of the Dynamics Navision, you must verify that the upgrade code units migrate data. Also the section for links to descriptions of deprecated functionality.

Upgrade Codeunits

When you introduce the changes to the database schema in the Microsoft Dynamics NAV 2018, Dynamics NAV will check if these changes are destructive or not. If the database check indicates that the change may lead to information deletion, such as if you are dropping the table column so that the contents of that column will be deleted, this is considered the destructive change. You will be prompted to handle the situation using upgrade core units.

Company Names

If the company name adds the special character, the error may show during the upgrade. In this context, special characters include the following:
[ ~ @ # $ % & * ( ) . ! % – + / = ? ]

If you are going to the Dynamics NAV upgrade a database where one or more company name involves the special character, we recommend you rename the company before you begin the upgrade process. After the upgrade is successfully done, you can rename the company again.

System Tables with Non-English Names

In the oldest versions of the Dynamics NAV, you could translate the columns in the system tables to the language other than English. Starting with version 3.0, we advised against this, and versions later than the Dynamics NAV require that all columns in all system tables are in English. As a result, if you try to open the database with non-English system tables in the Dynamics NAV or later, an error displays, saying that one or more columns do not exist.

Make sure that all objects were compiled in a development environment with the right.ETX and.STX files. You can confirm that you are running in the proper environment with English as the base language by opening the ndo$dbproperty table in the SQL Server Management Studio. In the Identifiers, a word Object must be written exactly as shown here.

Deprecated Fields and Fields Marked as Obsolete

Sometimes Microsoft will refactor the code so that fields are no longer used, or the functionality is moved from the base application to an extension, for example. The upgrade toolkit will manage the upgradation impact, but for the transparency, you can easily find the list of fields that are deprecated in the current release or marked to be obsolete in the later release.

Deprecated Fields and Fields Marked as Obsolete

In the Dynamics NAV, the number of fields have been deprecated in the current release or marked to be obsolete in a later release.

Definitions

Deprecated fields fall into 1 of the below groups:

  1. Fields moved to an extension by Microsoft

    Partner impact: Remember to install the extension when you upgrade the existing solution from an earlier version of the Dynamics NAV.

  2. Fields marked as Obsolete: PendingPartner impact: None in the current release, this is just a heads-up that a change is coming.
  3. Fields no longer in use in Microsoft codePartner impact: Refactor your code as soon as possible.

Fields moved to the extension by Microsoft in Microsoft Dynamics NAV 2018

The number of fields has been moved from the base application to an extension.

The functionality for payments and reconciliation has been moved to the Payments and Reconciliations extension.

Table ID Table Name Old Field ID New Field ID Old Field Name New Field Name
 23  Vendor  13650  13651  Giro Acc No.  GiroAccNo
 25  Vendor Ledger Entry  13650  13651  Giro Acc No.  GiroAccNo
 38  Purchase Header  13650  13651  Giro Acc No.  GiroAccNo
 79  Company Information  13600  13651  Bank Creditor No.  BankCreditorNo
 81  General Journal Line  13650  13651  Giro Acc No.  GiroAccNo
 122  Purchase Invoice Header  13650  13651  Giro Acc No.  GiroAccNo
 273  Bank Acc. Reconciliation  13600  13601  FIK Payment   Reconciliation  FIKPaymentReconciliation
 274  Bank Acc. Reconciliation   Line  13600  13601  Payment Reference  PaymentReference
 289  Payment Method  13601  13652  Payment Type   Validation  PaymentTypeValidation
 372  Payment Buffer  13650  13651  Giro Acc No.  GiroAccNo
 1226  Payment Export Data  13650  13651  Recipient Giro Acc No.  RecipientGiroAccNo
 1250  Bank Statement Matching   Buffer  13601  13652  Match Status  MatchStatus
 1250  Bank Statement Matching   Buffer  13600  13653  Description  DescriptionBankStatement

Fields no longer use in Microsoft code in Microsoft Dynamics NAV 2018

the number of fields that are related to the product groups is no longer in use because the feature was replaced by the item categories in the Dynamics NAV 2017. The fields are marked as ObsoleteState: Pending.

 Table ID  Field ID Comments
 5723   All  Deprecated. Do not use.
 27  5704  Will be removed in the later release.
 32  5707  Will be removed in the later release.
 37  5712  Will be removed in the later release.
 83  5707  Will be removed in the later release.
 111  5712  Will be removed in the later release.
 113  5712  Will be removed in the later release.
 115  5712  Will be removed in the later release.
 123  5712  Will be removed in the later release.
 125  5712  Will be removed in the later release.
 246  5705  Will be removed in the later release.
 753  5707  Will be removed in the later release.
 5108  5712  Will be removed in the later release.
 5110  5712  Will be removed in the later release.
 5741  5712  Will be removed in the later release.
 5745  5707  Will be removed in the later release.
 5747  5707  Will be removed in the later release.
 5902  5712  Will be removed in the later release.
 5991  5712  Will be removed in the later release.
 5993  5712  Will be removed in the later release.
 6651  5712  Will be removed in the later release.
 6661  5712  Will be removed in the later release.

Share This Post

Leave a Reply

avatar
  Subscribe  
Notify of
Skip to toolbar