1. CONVERTING YOUR CLASSIC CLIENT OBJECTS TO THE LATEST DYNAMICS NAV VERSION Per Mogensen

2. #NAVUGCongress16 We will cover the processes you will need to convert your objects from the “Classic-Only” Dynamics NAV version 5, through Dynamics NAV 2009, to the “RTC-Only” Dynamics NAV 2013 and beyond. These will include processes to convert your 2009 Form Objects to 2009 Page Objects, and converting 2009 Objects to 2013 Objects, including considerations for Object Types that you will not be able to carry forward. The processes will be demonstrated using small, simple examples. This session will not address converting reports, as that will be covered in "Upgrading your reports from Dynamics NAV 2009 Classic". DESCRIPTION

3. #NAVUGCongress16 Upgrading NAV 5.0 to 2009 R2 Upgrading Classic to RTC in NAV 2009 R2 Upgrading NAV 2009 R2 to 2013 Upgrading NAV 2013 to 2013 R2/2015/2016 AGENDA 3

4. #NAVUGCongress16 U PGRADING NAV 5.0 TO 2009 R2 4

5. #NAVUGCongress16 Database can be upgraded by opening with latest executable Code must manually be merged Data conversion require using NAV 2009 R2 before switch to NAV 2013 or later UPGRADING NAV 5.0 TO 2009 R2 5

6. #NAVUGCongress16 U PGRADING C LASSIC TO RTC IN NAV 2009 R2 6

7. #NAVUGCongress16 Forms to Pages Transformation tool allow avoiding manually recoding and test Report Request Form to Request page Transformation tool can also upgrade this MenuSuite conversion Transformation tool include upgrade of the MenuSuite too Dataports most be redesigned XMLPort is an option Consider using export/import from Excel or manually reading the file from code UPGRADING CLASSIC TO RTC IN NAV 2009 R2 7

8. #NAVUGCongress16 Tool create pages based on data and input data to control conversion Very powerful, but also time consuming to get the last 20% done Microsoft and many ISV use(d) this to develop one application but build for RTC too FORM TO PAGE TRANSFORMATION 8

9. #NAVUGCongress16 Transform existing Request Form to Request Page Is done with the transformation tool No input needed REPORT REQUEST PAGE 9

10. #NAVUGCongress16 Tool to work with the MenuSuite exported in text Add the Department on the MenuSuite MenuItems Un-supported object types must be removed Transform the Card->List to List->Card concept based on the Form transformation data MENUSUITE TRANSFORMATION 10

11. #NAVUGCongress16 U PGRADING NAV 2009 R2 TO 2013 11

12. #NAVUGCongress16 References in code like FORM.RUN is changed to PAGE.RUN Text file conversion tool is on the install DVD “UpgradeToolKit\Object Change Tools\TextFormatUpgrade2013.exe” Report changed from DataItem to RecordSet Require process to be run in development environment, process can only run if report compile Code is indented 7 extra spaces, making automated code merge hard UPGRADING NAV 2009 R2 TO 2013 12

13. #NAVUGCongress16 U PGRADING NAV 2013 TO 2013 R2/2015/2016 13

14. #NAVUGCongress16 Report upgrade RDLC from 2008 to 2010 format Makes it impossible to compare RDLC layout in text without upgrading the old reports to 2013 R2 format Only done during a complete database conversion, not when importing a single object Other updates to code done too Few technical changes require some objects from NAV 2013 R2 to be used MenuSuite Page for companies UPGRADING NAV 2013 TO 2013 R2/2015/2016 14

15. #NAVUGCongress16 Very simple upgrade of objects by importing and compiling No conversion of internal format in code Some.NET components have a version reference and can manually be adjusted UPGRADE NAV 2013 R2 TO 2015/2016 OR 2015 TO 2016 15

16. #NAVUGCongress16 Reminders: Please download the session slides from the NAVUG Congress Community or through the Congress App Please visit our Dynamics NAV help desk Monday evening in the Expo Please complete your session survey in the Congress App 16 THANK YOU FOR ATTENDING