We are upgrading from NAV 2016 to NAV 2018 Cum Update 4 on Premise (executable version is a little higher at 11.0.26401.0). We have 5 add-ons and a ton of customization's:
Also we are going with a Hybrid of C/AL and AL. I have moved all base page mods to Page Extensions in AL except for a handful of things that can't be done in AL yet. We use the Windows Client exclusively so no Web Client yet.
Here are a few things we have come across during the upgrade that I wanted to share and hope others will add on to this.
No longer works and Becomes:
Blue2 2. After the restructure of Item Category Code the upgrade toolkit updates any related document lines plus item ledger. This can be a very lengthy process based on your data. Adding some keys temporarily to the document lines such as Sales Shipment Line and Sales Invoice Line can greatly reduce the time in the data upgrade. The key you would want to add is Type,No. for the Document Line tables. 3.Make sure you get your upgrade toolkits for your add-ons. Some might not have one even though you might need it. I had to create a couple to make the Sync Schema For All Tables and Data Upgrade steps to work without issue. 4.When you "Sync Schema for All Tables" the first time do not use the Force option as it will skip the first step of the upgrade which is to move or copy data to temporary tables (TableSyncSetup Function) so you can move it back later on. This is very important since if you do force it will simply remove or delete data without the correct instruction to save it first so you can do something with it later. Make sure you really understand "Sync Schema for All Tables", "Data Upgrade" and the different types of upgrade codeunits before doing any of these steps. 5.Can't hurt to turn off change log while you run the Data Upgrade. Could increase your speed a bit.
Please add your own tips or tell me if I have anything wrong with these and I will correct it.
Jason good document. Everyone is contributing nicely.One thing when full testing is done and before the go live date.I strongly suggest uninstalling NAV 2016 or prior version from the server/workstations (With a reboot).Make sure NAV 2018+ is installed correctly and functioning.I've heard old Dll's were still in memory and Coding still pointing to old OCX/DLL/System objects.
Good luck and keep us posted with the testing and how many instances are you using?
1. NAVserver 1 and/or NAVserver 2
2. Job queue Instances.
3. Load Balancer if any.
4. Speed on database.
5. Also are you purging the Transaction log to increase the speed from the SQL database.
Good Luck, Thank you.
I thought I would add some more to this post that I started a while ago as we have been Live on NAV 2018 (on premise) for almost one month. Just a reminder, we upgraded from NAV 2016 and are now in a hybrid mode of AL and C/AL. Most of these issues would apply if you are upgrading to BC as well.
SalesHeader."Document Type" := SalesHeader."Document Type"::Order;
SalesHeader.Validate("Document Date","Document Date");
SalesHeader.VALIDATE("Sell-to Customer No.","Sell-to Customer No.");
Replace with something like this:
Thanks for keeping up with this. It will be extremely helpful to us when we make the move to 2018 (2019?). You truly are a Trail Blazer!
3150 SW 15th Street | Deerfield Beach, FL 33442
[o] 954-427-5711 x262 | [c] 561-523-1097
If you've found this thread useful, dive deeper into User Group community content by role