Migrating a 3.10 to 4.0; some object's issues

jclayton

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,

kine

You used Navision Developer Toolkit for merge process? If yes, it is normal that something is missing etc... it is why NDT is not used for this... Search the forum for NDT for some discussions about that problem.

kriki

Even with the best program available (don't which program this would be), a programmer has to check everything where a merge has occurred.
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.

jclayton

Well ...

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.