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