Open Forum

Expand all | Collapse all

Technical Upgrade to NAV 2017

  • 1.  Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted 09-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 09-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 09-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

    SILVER CONTRIBUTOR
    Posted 09-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 09-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 09-13-2017 07:49 AM
    Edited by Jason Wilder 09-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

    SILVER CONTRIBUTOR
    Posted 09-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 09-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 09-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 09-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 09-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

    SILVER CONTRIBUTOR
    Posted 09-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 09-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 09-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

    TOP CONTRIBUTOR
    Posted 09-22-2017 07:07 AM
    Tenerife is the development name for the next release of NAV.  NAV developers always use a code name for the new version they are working on. There was a lot of confusion at Directions regarding Microsoft's message on day one & two. It was clarified on Wednesday. (Directions is a partner meeting, in case you haven't heard of it before.)

    Look to hear a clearer message at Summit regarding Microsoft's new developments for NAV and Dynamics 365

    ------------------------------
    Ron Ketterling
    President
    Business Automation Specialists of MN, Inc.
    Minneapolis MN
    ------------------------------



  • 16.  RE: Technical Upgrade to NAV 2017

    Posted 09-21-2017 08:38 AM
    It depends on how current you are.  You can go from 2013 straight to 2017 (and presumably 2018), but if you're older than that, you have to make a brief stop at 2013.

    Ref: Upgrading to Microsoft Dynamics NAV 2017

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



  • 17.  RE: Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted 09-21-2017 09:43 AM
    We actually are hosted by a local service provider. They setup a new NAV server for the middle tier and a new Citrix server for the client. We then built a new database on the SQL Server, copied our NAV 2015 database to the new 2017 database. Once the middle tier was configured by our partner, we opened the database and in less than 15 minutes we were live on 2017. We tested for about two weeks and found no issues. We considered that a miracle because we are so highly customized.

    We then upgraded the client on the current Citrix servers and did a refresh of the 2017 database from our 2015 database on a Sunday. We shut down our 2015 NAV server and went live on Monday without a hitch. We run in virtual machines so we just archived the 2015 NAV server. A couple of weeks later, we deleted any 2015 databases.

    We did a CU a couple of weeks ago on a Sunday and it went just as smooth.

    We do plan to do the full upgrade next year, but we are on the fence about waiting for 2018. If the 2018 release is really delayed until Spring, we are more likely to upgrade to the full 2017 release.

    On a side note, we have been working diligently to use event subscriptions as much as possible to make the full upgrade easier. We may even move some of our existing customizations into Codeunits to further ease the upgrade process.

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



  • 18.  RE: Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted 11-08-2017 09:04 AM
    I started this post a while ago and have now officially upgrade our Production and have been live on this for 3 days (NAV 2016 CU14 to NAV 2017 CU10 Technical upgrade only).  There have been some issues (fortunately I have been able to work through most of them) that I would like to mention.  This wasn't as seamless as everyone else has posted so be prepared for a few things.

    • Report settings will be lost.  This is normal and you might expect this and as long as you are prepared it is no big deal.  People forget how to set the options on their reports and I would say about 50% of our issues were trying to remember the correct filters and options to set for things such as Batch Posting, Requisition Worksheet Calculate Plans, and some custom reports.  Have people take a screen shot of the options page before you upgrade.
    • Reports that are processing only that have filters but no requestpage use to save those filters automatically in NAV 2016.  Not the case with NAV 2017 so you need to go into the Requestpage on the report (even though it is empty) and make SaveValues = Yes and this will start saving your filters again.
    • Something has changed in regards to TransactionType in reports if it was set to Snapshot.  In NAV 2016 this was set on a few reports and basically locks the data before it runs the report so the report will balance.  An obvious example of this is account schedules.  If you don't lock the G/L Entry and Budget tables while you are getting the data there could be incomplete G/L entries that are brought into the data (I have seen this before).  In NAV 2017 it seems the fix is to change the TransactionType from Snapshot to the default which is UpdateNoLocks.  There was some different code as well in NAV 2017 so maybe they addressed this issue in some other way not sure.  The only out of the box place I have seen this is when in account schedules if you go to Accounts Overview, Actions, Export To Excel, Create New Document.  The error is scarey as can be seen here:
         The fix I used is to go to report 29 and change the TransactionType property to UpdateNoLocks
    • Something has changed in regards to TRY functions and using COMMIT.  It seems in NAV 2016 you could use a COMMIT in a TRY Function but in NAV 2017 you can't.  I haven't researched this yet so do not have more info.  When exporting ACH Payments (Out of the box) we recevied this error:

      To fix this I started to go down the path of grabbing 2017 objects having to do with custom layout and reports since this is where the error was coming from.  This quickly turned into a bad idea as many of these objects were dependant on other field and function changes so I abandoned this.  My final fix was in Codeunit 8800 I changed the GetRequestParameters function to no longer be a TRY function and in the InitializeData Function did this:
    //IF NOT GetRequestParameters THEN
    // Initialized := FALSE;
    GetRequestParameters; //Added this line
    This is generally what was done in NAV 2017 even though there is a ton more changes in NAV 2017 as well.
    Preview Posting
    • Another nice feature that no longer works due to the same change in behavior as listed above is the Preview Posting function for Sales Orders,  Purchase Orders, General Journals etc...  We now get the same error as above ("Call to the function 'LOCKTABLE' is not allowed inside the call to 'OnRun' when it is used as a TryFunction.").  I have not fixed this yet and it may not be worth the effort, not sure.
    • The Microsoft Dynamcis Add-in is not working for us.  When opening excel (where it tries to load this add-in) we get this error:
       So for now we have disabled the add-in and will not use this feature which most people in our company don't even know about anyway.

    Finally I will say that whenever we do an upgrade, people are looking for issues and will find a bunch of things that have nothing to do with the upgrade.  A nice approach is to make sure you have your old version (in our case NAV 2016) to prove out it is a new issue first.  The most bizarre things happened where I spent a few hours researching and turns out it was user error or had nothing to do with the upgrade.

    I am very happy that we have done this upgrade (and would do it again) but unfortunately one of our issues having to do with caching has not been resolved.  Supposedly the way caching was done on the service tiers was completely re-written in NAV 2017 so it is faster.  Not fixed.  Our Web Service tier can make a change to a record and the user (on a different service tier) will not see it sometimes for 15 to 30 seconds.  We have a complex environment with 4 service tiers so most of you probably won't run into this.  Some good things:
    • SQL Database Locks can be done int he developer environment and a job can be created to capture locks through the day if you want.
    • Export to Excel from a list is much better and faster (Excel button or Ctrl E)
    • Task Scheduler instead of Job Queue
    • Latest and greatest in regards to Web Client and Phone Client
    • Some new Developer commands
    • Save report settings on reports (which I don't understand how this works yet)
    • Performance and bug fixes

    Longest post ever, sorry for that!

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



  • 19.  RE: Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted 11-08-2017 09:10 AM
    @Gino Pack Good read!

    ------------------------------
    Cynthia Priebe, MCTS, DCP
    Senior Business Analyst and Project Manager
    Liberty Grove Software
    Grafton OH
    ------------------------------



  • 20.  RE: Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted 11-09-2017 09:24 AM
    Thanks so much for taking the time to share this, Jason! Awesome post!

    ------------------------------
    Greg Enns
    ERP Coordinator
    Technical Prospects
    Kaukauna WI
    ------------------------------



  • 21.  RE: Technical Upgrade to NAV 2017

    NAVUG ALL STAR
    Posted 11-09-2017 09:45 AM
    Well then @Jason Wilder gets the best answer award!  Thanks for kicking it up a notch Jason!


    ------------------------------
    Holly Kutil ~ NAVUG All-Star
    American Ring/Business Intelligence Dir.
    Solon, OH 44139
    **Great Lakes Chapter**
    ♥♥ Women In Dynamics ♥♥
    ------------------------------



  • 22.  RE: Technical Upgrade to NAV 2017

    TOP CONTRIBUTOR
    Posted 11-09-2017 12:34 PM
    Adding 2 more things we just found:
    • There is an option on the Service Tier called UI elements Removal which we have always (and still do) have set to LicenseFileAndUserPermissions.  It seems in NAV 2017 it will hide fields in a List page that have a table relation to a table that the user does not have access to.  NAV 2016 did not do this in List pages.  For example lets use a user who has access to the Customer table but not the Payment Terms table.  If the Customer List has the Payments Terms Code field on it, it would not show for this user.  The fix is to give the user Read permission for the related table.
    • In NAV 2016 if we were on a Customer Card and hit the Sales Order (New) button it would create a sales order and immediately insert the Sales Header and validated the Sell-To Customer No. so all the fields were filled in.  In NAV 2017 it puts your cursor in the Sell-To Customer No. field where you then have to hit Enter to get everything to populate.  SO the Sales Header is not inserted until you hit Enter.  This was a big deal for us since it broke some of our custom pages so I thought it worth mentioning.
    I had a thought that some of these behaviors I have mentioned here and above may be based on the Cumulative Update you are on, so you may or may not have the same experience.

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



  • 23.  RE: Technical Upgrade to NAV 2017

    SILVER CONTRIBUTOR
    Posted 11-13-2017 03:40 AM
    @Jason Wilder

    Thanks for the input, we make a technical upgrade in February next year.​
    Please keep us posted when you find more.

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