Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 272 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
NAD 2.0 -> 4.0 upgrade: Missing fields?
BrettB
Member Posts: 3
I am in the process of upgrading a Navision Advanced Distribution 2.0 database to 4.0, via a 2.0 -> 2.01 -> 2.6 -> 3.6 -> 4.0 path (path verified by MS's support dept.).
I've run into a bit of a roadblock with the 2.6 -> 3.6 phase. Several of the NAD fields were discontinued or renumbered in 3.6. When I try to import the new 3.6 objects into the upgraded database I receive error messages as it cannot delete populated fields.
The documentation is vague about this. Am I supposed to merge all of the legacy fields to the new table objects? By default, the merge tool drops the old fields. Or is there another conversion step that I missed? Also, does the conversion process delete these fields later on in the process?
Thanks to all in advance,
Brett
I've run into a bit of a roadblock with the 2.6 -> 3.6 phase. Several of the NAD fields were discontinued or renumbered in 3.6. When I try to import the new 3.6 objects into the upgraded database I receive error messages as it cannot delete populated fields.
The documentation is vague about this. Am I supposed to merge all of the legacy fields to the new table objects? By default, the merge tool drops the old fields. Or is there another conversion step that I missed? Also, does the conversion process delete these fields later on in the process?
Thanks to all in advance,
Brett
0
Answers
http://www.BiloBeauty.com
http://www.autismspeaks.org
Once I corrected this issue, the 3.6 objects imported correctly, and after much data crunching the 3.6 upgrade completed. The 4.0 upgrade was cake from there.
I am a little confused as to why one would suggest starting from scratch instead of going the upgrade route. The upgrade toolkits aren't perfect but they were sure a lot easier than trying to manually map the legacy data into import files.