You can simply open 2016 database in 2017 DEV Env and it will get converted to 2017. But - this is a 'technical' conversion - your application will still be NAV2016, although running in NAV2017 client. It will also probably fail in few places, like Job Queue, as there is a difference in handling TryFunctions between 2016 and 2017. Add-ons may need refreshing too.
The other way is to do a full upgrade. If you don't have any customisations you can use out of the box tools, otherwise, you need to merge code in customised objects. Part of the full upgrade is the 'technical' upgrade anyway.
One way or another your NST server would have to be upgraded too.
Answers
You can simply open 2016 database in 2017 DEV Env and it will get converted to 2017. But - this is a 'technical' conversion - your application will still be NAV2016, although running in NAV2017 client. It will also probably fail in few places, like Job Queue, as there is a difference in handling TryFunctions between 2016 and 2017. Add-ons may need refreshing too.
The other way is to do a full upgrade. If you don't have any customisations you can use out of the box tools, otherwise, you need to merge code in customised objects. Part of the full upgrade is the 'technical' upgrade anyway.
One way or another your NST server would have to be upgraded too.
Slawek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Zaid Tariq
Dynamics NAV/365 BC Developer at Dynamics 360
please like / agree / verify my answer, if was helpful.