In previous (classic) NAV versions, we could easily open a database with a higher NAV version, resulting in a 'technical' upgrade from the database. (no code / application upgrade) This was usefull to enable e.g. 'webservices' (feature from NAV 2009 R2) on a NAV 5.0 database.
Is this same approach still supported on RTC versions as well? Can we imagine opening a NAV 2009 / 2013 database in the NAV 2017 dev environment (possibly passing some intermediate versions), allowing the customer to connect to his same database, using the latest NAV 2017 client instead and use all old functionality (not using new NAV 2017 features such as Outlook integration, ...)?
0
Answers
2013 to 2016 doable - but fix the application objects needed by the executables.
2013 to 2017 - have not tried it, but with the trend to having more application objects ties to executables, it will probably take more fixing.
Best thing to do is upgrade everything.
http://mibuso.com/blogs/davidmachanick/