upgrade 3.70B to 4.0 SP1

nt
nt Member Posts: 160
hi all,
anyone can tell me what are the steps(procedures) that i have to do for upgrade a 3.70B to a 4.0 SP1.

there is document with that?

if there is more than 1 way to do this, which is the best an the easier?

thanks.

Comments

  • ara3n
    ara3n Member Posts: 9,258
    Please read the upgrade toolkit manual. It has all the steps and gives you options where you can take different routes, especially with merging objects.
    Ahmed Rashed Amini
    Independent Consultant/Developer


    blog: https://dynamicsuser.net/nav/b/ara3n
  • Eugene
    Eugene Member Posts: 309
    yes indeed i strongly recommend using upgrade toolkit

    basics steps are (not to be used as your guide but just to give you the feel of what is to be done):
    1) create a copy of your database
    2) open it with Nav 4.0 (even though your objects are still 3.70 version)
    3) import upgrade fobs provided with upgrade toolkit
    4) use those fobs to move your data to temporary tables in the same database
    5) upgrade your objects from 3.70 to 4.00
    6) import step2 fobs of upgrade toolkit that will move your data back from temp tables to the original ones (which have already been converted to 4.0 version in step5 )
  • kriki
    kriki Member, Moderator Posts: 9,132
    7) Do a lot of testing before doing the definitive upgrade!
    Regards,Alain Krikilion
    No PM,please use the forum. || May the <SOLVED>-attribute be in your title!


  • JK
    JK Member Posts: 21
    Check for known issues there is a big bug in upgrade tool related to Value entries!
  • Phenno
    Phenno Member Posts: 630
    JK wrote:
    Check for known issues there is a big bug in upgrade tool related to Value entries!

    how about more details?
  • colingbradley
    colingbradley Member Posts: 162
    Just done a 3.01 Native to 4 SQL

    Report 1001 will give different results if you use the Loaction filter, it looks like a Value Entry problem but it just the report has been changed so much you need to get the old version, fix it and then compare.

    Otherwise also be warned, SQL will object to some wrong dates that users may have entered so use the SQL Data test tools as well.
    Actually not a bad idea to fix up daft dates regardless.

    There is a document that describes in detail all the steps to be considered in pdf format, read it and highlight all the relevent bits and do plenty of testing.
    Experience is what you get when you hoped to get money