This is Part 5, the final part in our series on Upgrading from MS Dynamics NAV 2009 R2 to MS Dynamics NAV 2016. We suggest reading Part 1 , Part 2, Part 3 and Part 4 before continuing below.
 
Part 5: Upgrading to Dynamics NAV 2016

At the end of Part 4, the full upgrade from NAV 2009 R2 to NAV 2013 R2 was complete. It’s now time to upgrade from NAV 2013 R2 to NAV 2016. The steps here are similar to the previous upgrade in that you must convert the database, upgrade the code, then upgrade the data.
 
 
Upgrading to Dynamics NAV 2016 [NAV 2013 R2 -> NAV 2016]
 
Some things to consider before beginning the upgrade are the names of variables. If your current solution uses variables which are now used by a standard C/AL function (such as FOREACH), then those names must be changes, or must be enclosed in quotation marks. See the Changes in C/AL Behavior from Earlier Versions of NAV[1] article for more information on which names should not be used. Another thing that should be considered are deprecated/redesigned functionality. You must verify that the upgrade codeunits (which you can find more information about in the Upgrade Codeunits[2] article) migrate data correctly for the NAV 2016 upgrade[3].  Lastly, company names that include special characters should be renamed as this might cause errors during the upgrade, they can be restored once the upgrade is complete.
 
Converting the Databases [NAV 2013 R2 -> NAV 2016]
 
For this upgrade, you must first upgrade the NAV 2013 R2 database first, and then the application, then data later. The first step is to back up the old database and then prepare to convert it. Do this by making a copy or creating a full database backup[4]. You must then clear all NAV Server instance records from the dbo.Server Instance table in the database on SQL Server. This can be done by using SQL Server Management Studio to open and clear the table. Open the Development Environment and then connect to the old database[5], then verify that no objects are locked in the Object Designer. Open the Tools menu and choose Build Server Application Objects and then choose “Yes”. If errors occur, they will be shown in the Error List window and they must be addressed before continuing. Next, upload the NAV 2016 Partner Licence to the database. Since you are upgrading from NAV 2013 R2, you must run the Sync-NavTenant cmdlet from the NAV Administration Shell to synchronise the schema changes[6].
 
Now that the old database is prepared, the conversion can begin. You can now uninstall NAV 2013 R2 and then start the NAV 2016 installation. Run the setup and choose the Developer option. Once complete, open the NAV 2016 Development Environment and then connect to the database that was prepared earlier[7]. Read the instructions that appear in the dialog box carefully, as this action cannot be reversed. Choose OK and then OK again to confirm that you want to convert the database.
 
Once conversion is finished, connect a NAV 2016 Server instance to the converted database by using the NAV Server Administration Tool. You must also add the service account used by the NAV Server instance as a member of the db_owner role in the NAV database on the SQL Server[8][9].
 
Run the Development Environment as an administrator and then set the development environment to use the NAV Server instance that connects to the database[10]. Next, run the schema synchronization to complete the database conversion. Do this from the NAV Development Environment by going to Tools > “Sync. Schema For All Tables” > “With Validation” and then follow the synchronization instructions, or from the NAV 2016 Administration Shell by running the Sync-NavTenant cmdlet as follows[11]:
 
Scyn-NavTenant –ServerInstance <ServerInstanceName>
 
If the database references assemblies not included on the NAV 2016 installation media, add the assemblies to the Add-ins folder on the NAV Server (C:\Program Files\Microsoft Dynamics NAV\90\Service\Add-ins) or NAV Windows client computers (C:\Program Files (x86)\Microsoft Dynamics NAV\90\RoleTailored Client\Add-ins folder). Go back to the Development Environment and go to Tools > “Build Server Application Objects” and then choose Yes.
 
The next step is to fix compilation errors. If they occur, they would show up in the Error List window[12]. You can find a list of all objects that did not compile by setting a filter on the Object Designer in the Compiled field. Once complete, you must upload the customer licence to the converted database[13]. This will complete the conversion of the NAV 2013 R2 database to be able to be accessed from NAV 2016. To test the database, you can connect it to the NAV 2016 Server instance and then opening a client[14].
 
Upgrading the Application Code [NAV 2013 R2 -> NAV 2016]
 
Since we’ve already upgraded the application code to NAV 2013 R2, the changes to NAV 2016 should not be too large. To upgrade the application code, you must merge code form different versions of the application, this is called a code upgrade and must be completed before the data is upgraded.
 
The process of upgrading application code is similar to the one during the initial NAV 2009 R2 -> NAV 2013 R2 conversion, except that there are now cmdlets that can make things faster. Please see the article provided by Microsoft regarding the upgrade from NAV 2013 R2 Application Code to NAV 2016, which contains an overview and a detailed guide on this upgrade process[15].
 
Upgrading the Data [NAV 2013 R2 -> NAV 2016]
 
Upgrading NAV 2013 R2 data to NAV 2016 compatible data is also similar to the previous data conversion from the NAV 2009 R2 version. Data conversion tools are provided with NAV 2016 to convert old data with the old version’s table and field structure so that in functions with the new version’s table and field structure. Please see the article provided by Microsoft regarding the data upgrade to NAV 2016, which contains a list of prerequisites and a detailed list of all steps required for the data upgrade[16]. After the data has been upgraded, all three requirements for the NAV 2016 will be completed.

And that concludes our series on upgrading Dynamics NAV 2009 R2 to Dynamics NAV 2016!

If you found this series helpful and would like us to lead the upgrade of your company's system, don't hesitate to contact us.

[1] & [3] Upgrading to Microsoft Dynamics NAV 2016 - Upgrade Considerations

[2] Upgrade Codeunits

[4] Create a Full Database Backup (SQL Server)

[5] & [7] How to: Open Databases

[6] & [11] How to: Run the Sync-NAVTenant Cmdlet to Synchronize the Tenant Database with the Application Database

[8] How to: Connect a Microsoft Dynamics NAV Server Instance to a Database

[9] Provisioning the Microsoft Dynamics NAV Server Account

[10] How to: Change the Microsoft Dynamics NAV Server Instance

[12] Compilation Errors When Converting a Microsoft Dynamics NAV 2013 Database

[13] How to: Upload the License File

[14] Converting a Database

[15] Upgrading the Applications Code

[16] Upgrading the Data

This is Part 4 in our series on Upgrading from MS Dynamics NAV 2009 R2 to MS Dynamics NAV 2016. We suggest reading Part 1 , Part 2, and Part 3 before continuing below.
 
Part 4: Completing NAV 2009 R2 > NAV 2013 R2 Upgrade

When object and data conversion from NAV 2009 R2 to NAV 2013 R2 is complete, the next steps in completing the NAV 2009 R2 to NAV 3013 R2 upgrade are:

• Upgrading common data to all companies
• Deleting unused tables
• Testing the new database
• Upgrading specific applications

 
Upgrading Common Data to All Companies [NAV 2009 R2 -> NAV 2013 R2]
 
Common data that needs upgrading includes roles, database key groups, and Windows groups and the appropriate license type for NAV 2013 R2. If you have added, modified, or removed roles and permissions, you may have to upgrade these manually. Data included in non-company specific tables need to be manually upgraded since they are not upgraded by the upgrade tool. More information about upgrading roles and database key groups as well as Windows group licenses can be found in the Upgrading Data Common to All Companies[1] article.
 
Deleting Unused Tables [NAV 2009 R2 -> NAV 2013 R2]
 
Deleting obsolete tables and Upgrade Toolkit objects once upgrade is complete can be done by running page 104002 (Upgrade – New Version) from the Object Designer in the Development Environment. Choose the Mark Unused Old Tables option and then return to the Object Designer once complete. On the Version List column, set a filter for “Old Unused Table – marked for deletion” to see all the objects with this in its Version List. You must delete all these tables. Next, go back to Page 104002 again and choose Mark/Delete Upgrade Toolkit. This will delete all Upgrade Toolkit objects except for tables. To delete the tables, follow the same deletion process as above but with the filter “Upgrade Toolkit Table – marked for deletion”[2].
 
Testing the New Database [NAV 2009 R2 -> NAV 2013 R2]
 
To test the new database for errors that may exist after the upgrade, you must run the Development Environment and go to File > Database > Test. It is advisable to write test results to a file by choosing the Options tab in the Test Database dialog and choosing File, then entering a path. Test everything but the field relationships between tables by choosing a Normal test from the General tab, then test the field relationships separately by choosing “Test field relationships between tables” then Custom. Follow the workflow for repairing damaged databases and note the content and number off the field relationship tests if they cause an error. Verify that the customer’s license file includes all necessary permissions for the upgraded solution, then test the upgraded item ledger entry invoiced quantities to make sure that any date compressed entries have been upgraded correctly[3].
 
Specific Applications [NAV 2009 R2 -> NAV 2013 R2]
 
Specific application areas must also be upgraded on a table-by-table basis. These are not required for the upgrade to work, but are additional upgrades. The following articles can assist in this step: Upgrading Kitting to Assembly Management[4], Supply Chain Management Table Changes[5], Cost Accounting Table Changes[6], and Cash Flow Table Changes[7]. 

Stay tuned for Part 5. More information can be found in the cited links below.

[1] Upgrading Data Common to All Companies

[2] Deleting Unused Tables

[3] Testing the New Database

[4] Upgrading Kitting to Assembly Management

[5] Table Changes for Supply Chain Management

[6] Table Changes for Cost Accounting

[7] Tables Changes for Cash Flow

If you're finding this series helpful and would like us to lead the upgrade of your company's system, don't hesitate to contact us.

This is Part 3 in our series on Upgrading from MS Dynamics NAV 2009 R2 to MS Dynamics NAV 2016. We suggest reading Part 1 and Part 2 before continuing below.

Part 3: Importing Customized Objects and Completing Data Conversion

Once your NAV 2013 R2 Development Environment has been set up, and the NAV Server is connected to the new database, begin importing all customized objects into the NAV 2013 R2 database. It is important to import all the NAV 2013 R2 objects, as well as customized objects from NAV 2009 R2. To do this, you will need to create a combined export file (in text) with all the base and customized objects from NAV 2009 R2. You will need a merge tool that can display all three existing versions of the objects, which are the standard NAV 2009 R2 versions, Customized NAV 2009 R2 versions and the standard NAV 2013 R2 versions of the objects you have customized. This will assist in creating the new fourth merged file, the customized NAV 2013 R2 file. For more help in creating the new merged object file, read the following article, Merging[1], for a table that will help with creating the file.
 
Once the new merged file has been created, it should be imported into NAV 2013 R2 using the Object Designer. A warning may appear stating that some objects have conflicting versions. If that happens, press “OK” to run the Import Worksheet and choose the REPLACE ALL option, then click “OK”. Any errors in importing will cause the process to stop, so if they occur you must correct the issue in the new customized database (on NAV 2009 R2) and export the file again, then import it into NAV 2013 R2[2]. Compile all objects once they have been successfully imported into NAV 2013 R2.
 
Now that the majority of the conversion is complete, there are only a couple more things that must be done. You must import the “Upgrade601700.2” .fob file into the NAV 2013 R2 Development Environment. This can be found once again in either the Local Objects folder under the UpgradeToolKit directory (if you are upgrading a local version) or in the Data Conversion Tools folder if not upgrading from a local version. After importing, close the Development Environment and restart the NAV Server instance. Next, set the language of the customer database for each company. Set this from Tool > Language. Verify that the NAV Windows client works by running then closing it[3].
 
Since all the objects have been converted, the data must now be converted too. Open the Development Environment and the company you want to upgrade, then run page 104002 (Upgrade – New Version) from the Object Designer. Make sure the value for SQL Server Name is correct, if not you must update it. Choose Test Database Connection to verify the connection. Once complete, choose Transfer Data. To correct any errors, select the error then choose Show. This will open the relevant page and if possible will show the specific record with the error[4]. You must now complete the data changes by running page 257 (Source Codes) in the NAV Windows client and making note of any source codes that have been added. Update the Source Code and Source Code Setup tables for any additional source codes in the new version[5]. Finally, initialize the company by running codeunit 2 (Company-Initialize) from the Object Designer in the Development Environment, and repeat for each additional company in the database[6].

[1] Upgrading the Application Code - Merging

[2] Upgrading Company-Specific Data - Import All Customized Microsoft Dynamics NAV Objects       

[3] Upgrading Company-Specific Data - Data/Object Changes Prior to Step 2

[4] Upgrading Company-Specific Data - Step 2 Data Conversion

[5] Upgrading Company-Specific Data - Complete Data Changes After Step 2

[6] Upgrading Company-Specific Data - Initialize the Company

If you're finding this series helpful and would like us to lead the upgrade of your company's system, don't hesitate to contact us.

This is Part 2 in our series on Upgrading from MS Dynamics NAV 2009 R2 to MS Dynamics NAV 2016. To read Part 1, click here.

After upgrading the application code as noted in Part 1 of the series, the next step is to upgrade the data by using provisioned data conversion tools to convert the existing data with NAV 2009 R2’s table and field structure, so that it functions with NAV 2013 R2’s table and field structure.

Part 2: Upgrading the Data
 
Upgrading the Data [NAV 2009 R2 -> NAV 2013 R2]

Upgrading the NAV 2009 R2 database requires:

• Upgrading company-specific data
• Upgrading data common to all companies,
• Deleting unused tables
• Testing the new database

 
To upgrade company-specific data, follow the steps below. More details on the tasks below can be found in the Upgrading Company-Specific Data article[1].

• Open the NAV 2009 R2 Classic Client and make a copy/backup of the database that is being upgraded.
• Import the “Upgrade601701.1” .fob file found in the UpgradeToolKit directory of the NAV 2013 R2 installation files. The purpose if this import is to replace some tables to a clean state to prevent compilation errors in the future
• For each company in the database you will have to run the “Adjust Cost-Item Entries” batch job to make sure that the inventory cost data in the customer’s database is up-to-date

 
You are now ready to transfer the data. The following steps should be taken:

•  Run form 104001 (Upgrade - Old Version) from the Object Designer in NAV 2009 R2. Chose Transfer Data once for every company in the database.
• The Upgrade Error Log window will show any errors that need to be corrected that may occur.
• Run report 104001 (Table Information) to see the size of your database and make note of it as it will be needed later on when you set the size of the new database[2].

 
Once data transfer is complete, delete all non-table objects in the database, as well as tables that belong to features not available in NAV 2013 R2. To do this, simply run form 104001 again and chose Delete Objects. This will make sure that no conflicts or compilation errors occur during later tasks. A list of removed tables can be found in the Eliminated Tables[3] article.
 
The next task to perform is creating a new NAV database. Begin by creating another copy of the current database and then close and uninstall NAV 2009 R2. NAV 2009 R2 can be reinstalled later on. Ensure that the all the user permissions for the database are in place (see the “Preparing to Upgrade” section in Part 1). After that is done, it's time to install NAV 2013 R2 with the Developer Option. If using SQL Server 2008, set the compatibility level for the database to 100, otherwise set compatibility level to 110. This can be set from the SQL Server Management Studio after connecting the server instance that NAV is attached to.
 
Once installed, open the NAV 2013 R2 Development Environment and open the database that was copied before uninstalling NAV 2009 R2. This will prompt a database conversion which updates the system tables, enables Unicode in the database objects, upgrades to the newest Windows collation, and marks all objects in the database as not compiled. Once this step is complete, increase the size of the database to the size copied down earlier in this guide.
 
The next step is to upload your NAV 2013 R2 developer licence to the database and configure the NAV Server to connect to the new database. This can be done by starting the NAV Server Administration tool and selecting the appropriate NAV Server instance in the left pane. Choose Edit then update the database options to point to the converted database. Save once you are finished and restart the NAV Server instance[4].

Stay tuned for Part 3. More information can be found in the cited links below.

[1] Upgrading Company-Specific Data

[2] Upgrading Company-Specific Data - Step 1 Data Conversion

[3] Upgrading the Data - Eliminated Tables

[4] Upgrading Company-Specific Data - Create the New Microsoft Dynamics NAV Database

If you're finding this series helpful and would like us to lead the upgrade of your company's system, don't hesitate to contact us.

Many companies are deciding to make the switch from older Microsoft Dynamics NAV systems to the newer Dynamics NAV 2016. If you’re upgrading from NAV 2013, the process is relatively simple. However, if you’re currently using NAV 2009 R2, the upgrade process requires the additional step of upgrading to NAV 2013 first.

NAV 2009 R2 > NAV 2013 R2 > NAV 2016

We're breaking down the process in a multi-part series. If you have any questions or would like us to guide your company through this process, let's get in touch.
 
Part 1: Preparing to Upgrade and Upgrading the Application Code
 
Preparing to Upgrade [NAV 2009 R2 -> NAV 2013 R2]
 
Before beginning the upgrade, it’s important to note that the upgrade (to NAV 2013 R2) requires a 64-bit operating system and a 64-bit version of SQL Server[1]. There are also some actions that you should take before beginning the upgrade to NAV 2013 R2:

• Upgrading to NAV 2013 R2 from NAV 2009 R2 causes the link between interaction records and logged email messages to be lost. To resolve this, log all emails again to restore the links[2].
  
• If NAV 2009 R2 is used with a native NAV database, a migration must be performed to an SQL Server database.
  
• Verify that the user performing the upgrade has the necessary roles and permissions in SQL Server Management Studio. The user must have the “db_datareader”, “db_datawriter”, and “db_ddladmin” database roles for the database. The user must also have the “sysadmin” Server Role for the instance of SQL Server that is hosting the NAV database. The default schema for the user’s account must also be “dbo”.
• Ensure that the “superuser” is the one performing the upgrade and is the only one connected to the database,
• Ensure there are no locked objects in the Object Designer, the database has been backed up onto a safe location, and a copy of the customer’s database has been created.
• Database integration properties must also be disabled before the upgrade.

 
 
The final check before beginning the upgrade is to test the NAV 2009 R2 database to correct any errors if they exist. To test the database, you must run the test on the classic client. If the test fails, follow the workflow for repairing damaged databases. After testing, compile all the objects and make sure to repair any that are not compiling correctly[3].
 
It is also important to note that there may be some other product changes that may affect the upgrade, such as use of the Excel Buffer Export/Import, key generation and storage for payment services, change log support for sessions in multiple languages, and errors when importing XMLports.
 
Upgrading the Application Code [NAV 2009 R2 -> NAV 2013 R2]
 
The next step in upgrading from NAV 2009 R2 to NAV 2013 R2 is to upgrade the application code, thereby bringing forward the customizations made in NAV 2009 R2 to NAV 2013 R2. To do this, the application code must be upgraded by using a compare-and-merge process known as a code upgrade. The code upgrade is performed before the data upgrade.
 
The first step in the code upgrade is to update partner solutions. If there is a version of an add-on from a third-party, make sure that that add-on is compatible with NAV 2013 R2, or obtain the source code from the vendor and import it into the NAV 2009 R2 database before performing the upgrade. If there is no NAV 2013 R2 version of the add-on, you can choose to not transfer the third-party solution to NAV 2013 R2, or you can transfer the third-party solution to the target version as is and then do a code compare and merge for your standard application[4].

Stay tuned for Part 2. More information can be found in the cited links below.


[1] Upgrading to Microsoft Dynamics NAV 2013 - Introduction

[2] Troubleshooting: Email Logging

[3] Testing the Old Database

[4] Upgrading the Application Code - Updating Partner Solutions


If you're finding this series helpful and would like us to lead the upgrade of your company's system, don't hesitate to contact us.

The ‘Adjust Cost – Item Entries’ batch job is responsible for adjusting inventory values and records, in order to ensure that the correct costs are present in the general ledger and that all sales/profit statistics are up to date. When the batch job encounters value entries that need adjustment, it creates new adjustment value entries based off of information from the original value entries. The steps involved in this process are highlighted below:

a)   The batch process creates a new adjustment value entry, taking information from the original value entry, and adding the appropriate adjustment amount.

b)   When the adjustment entry is posted depends on one of two methods:

1. If inventory periods are used, then the posting date of the original entry is used, unless that date is in a closed inventory period. If that is the case, the new adjustment entry uses the starting date of the next open inventory period.
2. If inventory periods are not used, the posting date is defined by the ‘Allow Posting From’ field in the General Ledger.
   
   

c)   Navision calculates the adjustment based off of the ‘Costing Method’ chosen for each Item card.

The following costing methods are supported in Microsoft Dynamics NAV:

• FIFO (First In, First Out)
• LIFO (Last In, First Out)
• Average
• Specific
• Standard
  
  

Each of the costing methods mentioned above is described in detail at the following link: http://msdn.microsoft.com/en-us/library/hh997373(v=nav.71).aspx

*Please note: in order for the batch job to automatically update the general ledger, the user must select the ‘Automatic Cost Posting’ option in the inventory setup. If the user wishes to update the general ledger manually, they must run the ‘Post Inventory to G/L’ batch job.

Furthermore, the following options are available for the Adjust Cost – Item Entries batch report:

• Item No. Filter:Use this filter to run the batch job for only certain items.
• Item Category Filter: Use this filter to run the batch job for only certain item categories.
• Post to G/L:This function, along with the ‘Automatic Cost Posting’, allows the program to automatically post adjustments to inventory accounts in the general ledger. If this option is not selected, the user must run the ‘Post Inventory Cost to G/L’ batch job to guarantee that the appropriate general ledger accounts are updated.
  
  

*Please note: the Item No. and Item Category filters cannot be used together at the same time.
A periodic variant of the ‘Adjust Cost – Item Entries’ is offered through the ‘Automatic Cost Adjustment’ field in the ‘Inventory Setup’ table. This gives the user the option of automatically adjusting cost changes every time an inventory transaction is posted, using the following time periods:

Once an item’s cost has been adjusted (whether automatically or manually), the ‘Cost is Adjusted’ field on the item card is updated with a check mark. This check mark, which appears on any product order line for the item, signifies that the item’s cost has been updated.

Are you interested in implementing Microsoft Dynamics NAV at your business? Not sure which version is currently supported by your system? Use the tool below to help you figure out both the Dynamics NAV version and SQL Server version that are compatible with your edition of Microsoft Windows.

A flowchart highlighting system requirements for various editions of Microsoft Dynamics NAV.