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:
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.
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.
RSS Feed