Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K 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
- 295 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
Old Fields in NAV upgrade 3.6 to 5.0
Cindy101
Member Posts: 33
Hello,
I'm in the process of merging the customized objects from 3.6 with 5.0 sp1 objects and have gotten a bit stuck. I've run into many fields that were once in 3.6, but are no longer being used and are not in 5.0.
So far I've run into a dozen or so of them, and most of them were not being used in the 3.6 version of the client's DB, so I could just remove them, but some of them are populated and some with information that they most likely wan to save. A very good example is the contact field of the job table (62 - Contact), it looks like this was replaced with in 5.0 with Bill-to Contact (1003 - Bill-to Contact). My dev. license doesn't allow me to create a field in that range, so I'm thinking I could use a dataport in situations like this, but it seems there should be an easier way...
Any help would be greatly appreciated!
I'm in the process of merging the customized objects from 3.6 with 5.0 sp1 objects and have gotten a bit stuck. I've run into many fields that were once in 3.6, but are no longer being used and are not in 5.0.
So far I've run into a dozen or so of them, and most of them were not being used in the 3.6 version of the client's DB, so I could just remove them, but some of them are populated and some with information that they most likely wan to save. A very good example is the contact field of the job table (62 - Contact), it looks like this was replaced with in 5.0 with Bill-to Contact (1003 - Bill-to Contact). My dev. license doesn't allow me to create a field in that range, so I'm thinking I could use a dataport in situations like this, but it seems there should be an easier way...
Any help would be greatly appreciated!
0
Answers
RIS Plus, LLC
MVP - Business Apps