Open Forum

Hi GPUGers.

I'm planning our next upgrade from version 2016 R2 to 2018.3.  Past upgrades have not changed much in structure since version 2010.
I am wondering if there are any notable changes to the upgrade process that I need to plan for.
Also, is there a single web page or slide deck with a good summary of added features since version 2018 was introduced?
Thanks for your comments.
#Admin #Upgrades

------------------------------
Lou Spevack
American Council on Education
Washington DC
------------------------------

Terry R Heley  Does a great blog on upgrades.

------------------------------
Dan Bigelow
mbsPartners
Los Angeles CA
------------------------------

Original Message:
Sent: Feb 11, 2021 07:13 AM
From: Lou Spevack
Subject: Upgrade Planning

Hi GPUGers.

I'm planning our next upgrade from version 2016 R2 to 2018.3.  Past upgrades have not changed much in structure since version 2010.
I am wondering if there are any notable changes to the upgrade process that I need to plan for.
Also, is there a single web page or slide deck with a good summary of added features since version 2018 was introduced?
Thanks for your comments.
#Admin #Upgrades

------------------------------
Lou Spevack
American Council on Education
Washington DC
------------------------------

Lou,
back when I was at GPUG - a group of folks created a great multi-page checklist.  This could be updated to help you:  see attached:  Upgrade Checklist

------------------------------
Kim Peterson
701-261-7307
Kim@DynamicsConnections.com
#KimPetersonGP
------------------------------

Original Message:
Sent: Feb 11, 2021 07:13 AM
From: Lou Spevack
Subject: Upgrade Planning

Hi GPUGers.

I'm planning our next upgrade from version 2016 R2 to 2018.3.  Past upgrades have not changed much in structure since version 2010.
I am wondering if there are any notable changes to the upgrade process that I need to plan for.
Also, is there a single web page or slide deck with a good summary of added features since version 2018 was introduced?
Thanks for your comments.
#Admin #Upgrades

------------------------------
Lou Spevack
American Council on Education
Washington DC
------------------------------

Upgrades can go easy (almost) every time, with planning, and lots of practice in a test environment. Don't forget the 3rd party apps!

Make sure you understand and plan for the Microsoft "Modern Lifecycle".
What does Modern Lifecycle mean for Microsoft Dynamics GP? - Microsoft Dynamics GP Community


------------------------------
David Morinello
Senior Dynamics GP Systems Architect
Ascend Learning, LLC
Leawood KS
------------------------------

Original Message:
Sent: Feb 12, 2021 01:34 AM
From: Kim Peterson
Subject: Upgrade Planning

Lou,
back when I was at GPUG - a group of folks created a great multi-page checklist.  This could be updated to help you:  see attached:  Upgrade Checklist

------------------------------
Kim Peterson
701-261-7307
Kim@DynamicsConnections.com
#KimPetersonGP

Original Message:
Sent: Feb 11, 2021 07:13 AM
From: Lou Spevack
Subject: Upgrade Planning

Hi GPUGers.

I'm planning our next upgrade from version 2016 R2 to 2018.3.  Past upgrades have not changed much in structure since version 2010.
I am wondering if there are any notable changes to the upgrade process that I need to plan for.
Also, is there a single web page or slide deck with a good summary of added features since version 2018 was introduced?
Thanks for your comments.
#Admin #Upgrades

------------------------------
Lou Spevack
American Council on Education
Washington DC
------------------------------

As always, your best friend is a test environment in which to do a test upgrade or two.  I would definitely check out the list from @Kim Peterson, but here's a short list from my Upgrades class (which I'm scheduled to present again as a GPUG webcast on March 18th):

1) How many companies?  Are they similar or different?  Upgrades for only a single company are usually simpler and take much less time than upgrades for a large number of companies with different GL accounts or especially modules.
2) The Server.  What is the Operating System?  What is the SQL Server version?  Are they compatible with the version of GP you want to upgrade to?  If you are using mapped drives or other server resources, are there any changes there to consider?
3) Reports.  Check your report dictionaries and .SET files.  Also look at your external reporting such as Excel-based reports, SSRS, Management Reporter, FRX, etc.  If you're doing an in-place upgrade there may be less to worry about than in the case of a server move.
4) Integrations.  Whether you are using Integration Manager, Smart Connect, or something else, almost every system consumes information from outside sources.  This can include EDI sources.
5) Special modules like Manufacturing.
6) Third-Party modules (Rockton, Salespad, etc.)  These have their own versions specific to the GP version you are going to upgrade to.  Make sure to acquire the new installers and test them as part of testing your entire upgrade process.
7) Other applications which use GP data
8) Citrix or Remote Desktop Server.  These can present additional issues on top of everything else.
​
I also have developed a few custom SQL scripts which I found useful in identifying potential problem spots.  Email me directly if you are interested in trying them out.

------------------------------
Blair Christensen
Database Administrator
Oppenheimer Companies, Inc.
Boise Idaho GPUG Chapter Leader
------------------------------

Original Message:
Sent: Feb 11, 2021 07:13 AM
From: Lou Spevack
Subject: Upgrade Planning

Hi GPUGers.

I'm planning our next upgrade from version 2016 R2 to 2018.3.  Past upgrades have not changed much in structure since version 2010.
I am wondering if there are any notable changes to the upgrade process that I need to plan for.
Also, is there a single web page or slide deck with a good summary of added features since version 2018 was introduced?
Thanks for your comments.
#Admin #Upgrades

------------------------------
Lou Spevack
American Council on Education
Washington DC
------------------------------

I appreciate all the excellent answers.  My takeaway is that not much has changed.
I've done dozens of upgrades in the past and but my last one was in 2017.
My experience is that it's important to read the upgrade.pdf document for each new version.  While 95% stays the same, there's always something new in the weeds. Then it's plan, test, test again and plan more.
I also need to go through all the new features since 2018 and identify which ones to test, implement and train users on.  So a single site with a good feature summary will be helpful.  Terry Heley's blog is a good one.  Part of a successful upgrade is selling the new feature sizzle.
Many thanks.


------------------------------
Lou Spevack
American Council on Education
Washington DC
------------------------------

Original Message:
Sent: Feb 12, 2021 10:27 AM
From: Blair Christensen
Subject: Upgrade Planning

As always, your best friend is a test environment in which to do a test upgrade or two.  I would definitely check out the list from @Kim Peterson, but here's a short list from my Upgrades class (which I'm scheduled to present again as a GPUG webcast on March 18th):

1) How many companies?  Are they similar or different?  Upgrades for only a single company are usually simpler and take much less time than upgrades for a large number of companies with different GL accounts or especially modules.
2) The Server.  What is the Operating System?  What is the SQL Server version?  Are they compatible with the version of GP you want to upgrade to?  If you are using mapped drives or other server resources, are there any changes there to consider?
3) Reports.  Check your report dictionaries and .SET files.  Also look at your external reporting such as Excel-based reports, SSRS, Management Reporter, FRX, etc.  If you're doing an in-place upgrade there may be less to worry about than in the case of a server move.
4) Integrations.  Whether you are using Integration Manager, Smart Connect, or something else, almost every system consumes information from outside sources.  This can include EDI sources.
5) Special modules like Manufacturing.
6) Third-Party modules (Rockton, Salespad, etc.)  These have their own versions specific to the GP version you are going to upgrade to.  Make sure to acquire the new installers and test them as part of testing your entire upgrade process.
7) Other applications which use GP data
8) Citrix or Remote Desktop Server.  These can present additional issues on top of everything else.
​
I also have developed a few custom SQL scripts which I found useful in identifying potential problem spots.  Email me directly if you are interested in trying them out.

------------------------------
Blair Christensen
Database Administrator
Oppenheimer Companies, Inc.
Boise Idaho GPUG Chapter Leader

Original Message:
Sent: Feb 11, 2021 07:13 AM
From: Lou Spevack
Subject: Upgrade Planning

Hi GPUGers.

I'm planning our next upgrade from version 2016 R2 to 2018.3.  Past upgrades have not changed much in structure since version 2010.
I am wondering if there are any notable changes to the upgrade process that I need to plan for.
Also, is there a single web page or slide deck with a good summary of added features since version 2018 was introduced?
Thanks for your comments.
#Admin #Upgrades

------------------------------
Lou Spevack
American Council on Education
Washington DC
------------------------------