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