Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 269 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
Migrating a 3.10 to 4.0; some object's issues
jclayton
Member Posts: 3
Hi y'all,
We used the Upgrade tool kit for migrating a 3.10 to a 4.0 and after the whole process, we end up with a 4.0 with some issues:
1) Missing Keys & SIFTs on tables. Some KEYS were apparently migrated but dome others were not.
2) Missing Personalized MenuButtons on some estandar FORMs.
3) Missing Personalized Fields, when these fields are on estandar pagenames.
4) Apparently No Detection on code based upon 3.01 standard functionality Non existent on 4.0, were not indicated during the process so it could not be fixed.
5) During the migration process, some problems arised but were fixed by splitting some Codeunits/process or making temporary tables not temporary (because of files exceeding 2 Gb of size Navision Problem).
We are just wondering if someone made this before and could orient us a little ( ](*,) ).
Thanks in advance,
We used the Upgrade tool kit for migrating a 3.10 to a 4.0 and after the whole process, we end up with a 4.0 with some issues:
1) Missing Keys & SIFTs on tables. Some KEYS were apparently migrated but dome others were not.
2) Missing Personalized MenuButtons on some estandar FORMs.
3) Missing Personalized Fields, when these fields are on estandar pagenames.
4) Apparently No Detection on code based upon 3.01 standard functionality Non existent on 4.0, were not indicated during the process so it could not be fixed.
5) During the migration process, some problems arised but were fixed by splitting some Codeunits/process or making temporary tables not temporary (because of files exceeding 2 Gb of size Navision Problem).
We are just wondering if someone made this before and could orient us a little ( ](*,) ).
Thanks in advance,
0
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
It is possible that in a certain point the 2 base versions of Navision differ AND in the same point some localisation has occured. In this case only a seasoned programmer knows what to take or do.
I have done already a lot of merges and in general no big problems occur, because after the merge I check all the points where some merge has occured. The only problem is that this is something you can't do for a whole day because your eyes go nuts.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
We used to make migrations the old way ... by comparing each object and make the necessary corrections and creating the appropiate Dataports/Process to migrate all data...
Seems that we have a bunch of work in front then ...
Thank You very much guys for your prompt response.