mibuso.com
Home› NAV Three Tier
Options

Upgrading from NAV2009 RTM to NAV2015 CU4

JostoJosto Member Posts: 8
edited 2015-05-06 in NAV Three Tier
Hi all.

We have a NAV2009 RTM (Build 27808) with a Database converted (several years ago) from NAV 5.0 to 2009 (convert was performed opening with the 2009 Classic Client) so, there are a lot of objects in versión 15.00 and some in Versión 16.00. There are about 100 customized objects between tables, Forms, codeunits and reports (10 of them with a heavy customization).

The idea is upgrade to NAV 2015 CU4. According with the documentation, the upgrade should be made from NAV 2013 or NAV2009 (R2 or SP1) and, in my kwnoledge, that implies:

1) Upgrade from NAV2009 RTM To NAV2009 SP1 (Data + Code)
2) Upgrade from NAV2009 SP1 to NAV2015 CU4 (Data + Code)

I realized that, maybe I could simplify the process in the following way:

1) Upgrade fron NAV2009 RTM TO NAV2015 CU4 (only the CODE with merge tools and so...)
2) Upgrade from NAV2009 RTM To NAV2009 SP1 (only the DATA) and FROM NAV2009 SP1 to NAV2015 CU4 (only the DATA).

What do you think about this? Is it the right way to go? problems? Any way to simplify more?

Thanks in advance

Comments

  • Options
    davmac1davmac1 Member Posts: 1,283
    You only need to upgrade the data to 2009SP1 which means adding any new NAV fields to table - code logic not required.
    Then to upgrade to 2015, you should bring your mods into 2015 if you plan to keep them.

    Also, before you start, remove any junk tables - prior upgrades, unused add-ons, etc.
    David Machanick
    http://mibuso.com/blogs/davidmachanick/
  • Options
    JostoJosto Member Posts: 8
    Hi, David

    Thanks for your answer.

    How can I bring only the new fields to table? (and new tables of SP1, I suposse). Is enough opening the database with the 2009SP1 Classic client for generate them or Will i have to use any merge tool to add these fields to the tables?

    Regards.
  • Options
    davmac1davmac1 Member Posts: 1,283
    You can merge new-> existing.
    You may have to strip out the code first in 2009 since the merge will not work when there are compile errors.
    David Machanick
    http://mibuso.com/blogs/davidmachanick/
  • Options
    JostoJosto Member Posts: 8
    Hi, David.

    Thanks again.

    Which is the fastest way to strip out the code? (Sorry if the answer is obvious, I´m newbie).

    According your recomendations my plan for upgrading is the following:

    1) Merge the customizacions of my current NAV 2009 with the NAV 2015 CU4 following the standard procedures generating the new objects

    2) Create the new fields and so in the NAV2009 with following your recomendations and convert the db to NAV2009 SP1

    3) Migrate the Data from the NAV 2009 SP1 to NAV 2015 CU4 following the standard procedures

    What do you think?

    Regards.
  • Options
    davmac1davmac1 Member Posts: 1,283
    That sounds about right.
    As far as stripping out code, load up a 2009 SP1 Cronus demo database and strip out the code from the new field numbers.
    Not all code will give you problems, but since this is a data only upgrade, you don't care about the code at this stage.
    Then do your merge new --> existing and it will add the new field numbers.
    David Machanick
    http://mibuso.com/blogs/davidmachanick/
  • Options
    KowaKowa Member Posts: 918
    Josto wrote:
    Which is the fastest way to strip out the code?
    You can use this new tool:
    http://www.mibuso.com/dlinfo.asp?FileID=1649
    Kai Kowalewski
Sign In or Register to comment.