upgrade using cutoff approach

sendohsendoh Member Posts: 207
hi guys,

is it ok to make an upgrade by simply import the data from say 3.7 to 5.0.

example

we will use the version 5.0(setup,master data according to 3.7 version) on august, then we will just import the data of ledger entries from 3.7 and the customized object.

by doing this we don't have to make an object and data upgrade.

what should be the problem using this approach?

regards ,

Sendoh
Sendoh
be smart before being a clever.

Comments

  • KarenhKarenh Member Posts: 209
    I think that approach is likely to cause problems. There are new fields, and some objects expect there to be values in the new fields.

    I would follow the upgrade process that is included with the Developer's Toolkit, and use the data conversion tools provided.
  • vanrofivanrofi Member Posts: 272
    and hurry up...you have 2 weeks left...
  • Alex_ChowAlex_Chow Member Posts: 5,063
    sendoh wrote:
    hi guys,

    is it ok to make an upgrade by simply import the data from say 3.7 to 5.0.

    example

    we will use the version 5.0(setup,master data according to 3.7 version) on august, then we will just import the data of ledger entries from 3.7 and the customized object.

    by doing this we don't have to make an object and data upgrade.

    what should be the problem using this approach?

    regards ,

    Sendoh

    NOOOOO!!!!!!! :shock:

    You will be in a world of hurt. You can probably write a book with the problems you'll encounter.

    Don't make your own rules, follow the upgrade toolkit. It's created for a reason.
  • sendohsendoh Member Posts: 207
    thanks to may consultants here in mibuso :lol:
    Sendoh
    be smart before being a clever.
Sign In or Register to comment.