Upgrade 5.1 to 2009
tiamat
Member Posts: 1
Hello,
I have a Nav 5.1 in production, and i want to (for now) migrate to 2009 R2.
The conversion for the classic client is ok. Everything works perferctly.
The next step is to progressly migrate with RTC.
How can i import the 2009 objects on my installation. I don't want to loose the specific fields, codeunits .. I understand i have to recretate all the reports and the pages, but i want to keep the cronus one for begining.
so i want my old 5.1 datas (tables + codeunits + dataport) and the new 2009 datas (pages, reports, updated codeunits, updated tables)
is it possible ?
is there is a merge tools ?
Thanks.
Tiam.
I have a Nav 5.1 in production, and i want to (for now) migrate to 2009 R2.
The conversion for the classic client is ok. Everything works perferctly.
The next step is to progressly migrate with RTC.
How can i import the 2009 objects on my installation. I don't want to loose the specific fields, codeunits .. I understand i have to recretate all the reports and the pages, but i want to keep the cronus one for begining.
so i want my old 5.1 datas (tables + codeunits + dataport) and the new 2009 datas (pages, reports, updated codeunits, updated tables)
is it possible ?
is there is a merge tools ?
Thanks.
Tiam.
0
Answers
-
Hi,
There is a transformation tool in the root of installation DVD. There are also some readme files and transformation script samples.
The first step is technical conversion to 2009 R2. As I understand you have already done it.
The next step is to convert custom and modified pages (non-modified pages can be imported from Cronus.
The process is bascialy export forms in text, convert, import pages, see what is not compiling/missing, change the code on the form and/or change conversion rules, export, convert...
It may be easier to take standard page and code merge changes - all depends what and how was customized.
It is good to move all or most of the code off the pages into codeunits or tables, leaving only code dealing strictly with UI. This is also a part of good practice/NAV recommended design patterns As a minimum I'd suggest to move all the code from triggers/controls on forms into local functions.
I've seen a tool in Download section which automates most of the export/convert/import process, it may save you a few clicks/renames
SlawekSlawek Guzek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-030
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 329 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
