Open Forum

 View Only
Expand all | Collapse all

Technical Upgrade to NAV 2017

  • 1.  Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted Sep 08, 2017 08:05 AM
    We are going to do a technical upgrade from NAV 2016 CU14 (9.0.47444) to NAV 2017 latest version.  No code will be upgraded unless we find issues.  There are some performance fixes plus the SQL locking tool in the dev environment that are some of the main reasons for doing this.

    Has anyone done this and run into any issues that you could share?

    ------------------------------
    Jason Wilder
    Senior Application Developer
    Stonewall Kitchen
    York ME
    ------------------------------


  • 2.  RE: Technical Upgrade to NAV 2017

    Posted Sep 11, 2017 02:25 AM
    We have not done this, but here is a post where one or two things are mentioned.

    https://dynamicsuser.net/nav/b/mark_brummel/posts/nav2017-why-is-it-so-damn-fast

    ------------------------------
    Kevin Ball
    Rajapack GmbH
    Ettlingen
    ------------------------------



  • 3.  RE: Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted Sep 11, 2017 03:21 PM
    We have done this without any issues.

    ------------------------------
    Gregory Alford
    ERP Manager
    Tri Star Metals LLC
    Carol Stream IL
    ------------------------------



  • 4.  RE: Technical Upgrade to NAV 2017

    GOLD CONTRIBUTOR
    Posted Sep 12, 2017 04:41 AM
    ​Hi,
    We are planning a technical upgrade from NAV2013R2 to NAV2017.
    Does anyone have experience with this?

    ------------------------------
    Annette van der Muur
    Hal Leonard
    The Netherlands
    ------------------------------



  • 5.  RE: Technical Upgrade to NAV 2017

    Posted Sep 12, 2017 11:28 AM

    ​Hello,

    We would also like to perform a Technical Upgrade from NAV 2013 R2 to NAV 2017.  Pre-RTC is seemed to be a Microsoft best practice to be on the latest executables which included major releases or crossing from 4.0 to 5.0 for example.  That practice seemed to change with the release of the 3 Tier Architecture.  Now I have found some documentation on MSDN that leads me to believe Microsoft may be recommending / supporting this type of upgrade.  Please review this link:  Converting a Database - Technical Upgrade

    We have been trying to get our VAR to verify this with Microsoft to ensure this is truly supported and/or recommended for several months without a clear answer.  :(
    Our goal is to be able to minimize our customization footprint by taking advantage of events.  I have tested this with a Cronus database (2013 R2 to 2016) and events seem to work fine.  With that said, we also don't want to perform this technical upgrade if Microsoft is not willing to support it.  The above posting implies they will to me, but we need confirmation from Microsoft.

    If others have performed a Technical Upgrade from a Platform without Events to one with Events I would be interested in hearing your perspective.

    Thanks,



    ------------------------------
    Jeff Halat
    Senior NAV Developer
    Ortho Molecular Products, Inc
    Woodstock IL
    ------------------------------



  • 6.  RE: Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted Sep 13, 2017 07:49 AM
    Edited by Jason Wilder Sep 13, 2017 07:50 AM
    I just noticed in NAV 2017 service tier there is a property called Build Restriction (turns out this existed in NAV 2016 as well, just never noticed it).  Options are AlwaysConnect, WarnClient and DoNotAllow.  Thought I would mention this since it seems Microsoft is now allowing different versions to work with each other.  I am now curious if our NAV 2016 clients will work with NAV 2017 service tier.  Not planning on doing this in our production environment but I will post more once I am done with the Technical upgrade.

    The actual piece that upgrades the database took about 10 minutes.  Now I am working on getting the first service tier up and running.

    ------------------------------
    Jason Wilder
    Senior Application Developer
    Stonewall Kitchen
    York ME
    ------------------------------



  • 7.  RE: Technical Upgrade to NAV 2017

    GOLD CONTRIBUTOR
    Posted Sep 14, 2017 03:56 AM
    ​Herewith the official reaction of Microsoft

    Technical upgrades from older version than 2015 are not allowed to NAV 2017, we simply do not support it because of the changes we have had in the platform, which makes it unstable and the integrity of it would be not possible to expect.

    We do support happily the technical upgrade possibility from NAV 2016 to NAV 2017, and from NAV 2015 to NAV 2016, we started supporting this again starting from NAV 2015, because we have done a lot of work on the platform to enable this in a safe way, starting from how the objects are being dealt with, the metadata, and the schema sync, only starting from NAV 2015 is this unified, the versions before are definitely far to different, hence we couldn't afford allowing the technical upgrade form them.

    NAV 2013 R2 is a version to be known having some difficulties when it comes to schema sync and table metadata, so I would definitely advise you, to leave this version to any higher one only based on a full upgrade path, then as I said starting from NAV 2015 it gets more stable.


    I know of only one successfull technical upgrade from NAV2013R2 to NAV2017 in the Netherlands.

    I would prefer a tecnical upgrade to have the better performance very quick and make the offical functional upgrades later.

    ------------------------------
    Annette van der Muur
    Hal Leonard
    The Netherlands
    ------------------------------



  • 8.  RE: Technical Upgrade to NAV 2017

    Posted Sep 14, 2017 08:35 AM
    I had never considered the possibility of splitting the upgrade process into technical and functional pieces.  I quite like the idea of doing a technical upgrade from 2016 to 2017, and a functional upgrade later.  I'm watching this thread to see what your experience is.
    Thanks,
    CF

    ------------------------------
    Chris Frazier
    Business Analyst Manager
    Audiology Management Group
    Stockton MO
    ------------------------------



  • 9.  RE: Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted Sep 15, 2017 08:10 AM
    After doing the Technical upgrade from 2016 to NAV 2017 CU10 (just released in Sept) here are a few more findings:
    You do need to upgrade the client to NAV 2017 even though there is the property in the service tier I mentioned above.
    It seems in my little testing so far that I do not require a NAV 2017 license to upgrade or use NAV 2017.  Not that you would want to do this but just wanted to mention.

    The only stopper so far is an error when you log in based on table 5330 "CRM Connection Setup".  Here is a thread from Microsoft that solves this problem (basically a missing dll):
    https://msdn.microsoft.com/en-us/dynamics-nav/resolve-table-5330-error-converting-database

    I am pleased with the performance so far but will post when I have more solid results.

    ------------------------------
    Jason Wilder
    Senior Application Developer
    Stonewall Kitchen
    York ME
    ------------------------------



  • 10.  RE: Technical Upgrade to NAV 2017

    GOLD CONTRIBUTOR
    Posted Sep 18, 2017 09:42 AM
    This is something I would be interested in doing with our NAV2016 CU6 Install.  Currently we have one issue with Shortcut Dim Codes that I believe is a Client issue and not NAV Code Related.  The issue is that if you show the column for the Dim Code on a PO Line for example and you enter the data on the line it does not save the value.  We have seen this on multiple pages in NAV.

    The work around I have found is the set the Shortcut Dim Field Property to Visible on the Page and it works fine.

    I also miss not having the Tool to figure out who is locking what for tables.

    Keep us posted on how this works out for you.

    ------------------------------
    Justin Falconer
    IT Manager
    Tender Corporation
    Littleton NH
    ------------------------------



  • 11.  RE: Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted Sep 20, 2017 11:30 AM
    I'm thinking about doing it, but I was going to wait until 2018 gets released in a couple of months!

    As I understand it, you have to go from one version to the next, one at a time, you can't go straight from the current version to the latest.

    Can anyone verify that?

    ------------------------------
    Val Gameiro
    Senior NAV Analyst
    BPL Plasma
    Austin, Texas
    ------------------------------



  • 12.  RE: Technical Upgrade to NAV 2017

    GOLD CONTRIBUTOR
    Posted Sep 21, 2017 06:24 AM
    ​It seems that NAV2018 will be released spring 2018, we have to be patience.

    It's correct that you have to go through all versions for a functional upgrade. Microsoft does not support you, when you skip one.
    However it's possible to do more than one upgrade in one project. You only have to test the last upgrade with your users. That saves time.

    ------------------------------
    Annette van der Muur
    Hal Leonard
    The Netherlands
    ------------------------------



  • 13.  RE: Technical Upgrade to NAV 2017

    NAVUG ALL STAR
    Posted Sep 21, 2017 08:20 AM
    Just released this week:
    New NAV will be Dynamics 365 Tenerife

    You can read the full article here....

    https://community.dynamics.com/nav/b/totovicnavblog/archive/2017/09/17/new-nav-will-be-dynamics-365-tenerife

    ------------------------------
    Holly Kutil
    American Ring/NAV Admin
    Solon, OH 44139
    **Great Lakes Chapter**
    ♥♥ Women In Dynamics ♥♥
    ------------------------------



  • 14.  RE: Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted Sep 21, 2017 01:03 PM
    Microsoft appears to be backing off a couple of the announcements.

    It doesn't appear we know when Tenerife will be released. It may be sooner than Spring 2018.

    There will also apparently not have to be a white-labeled "Ian's Awesome Networked Resource-planning and Yammer suite - powered by Dynamics 365."

    ------------------------------
    Ian Ray
    Cypress Grove
    Arcata CA
    ------------------------------



  • 15.  RE: Technical Upgrade to NAV 2017