Microsoft Dynamics GP Great Plains Upgrade FAQ

Jul 25
19:08

2007

Andrew Karasev

Andrew Karasev

  • Share this article on Facebook
  • Share this article on Twitter
  • Share this article on Linkedin

Currently the latest version is 10.0. It is also common situation when ERP version is not current, but, say 2, 3 or even 5 years old. There are several version upgrade strategies. One of them is to go pace-in-pace with Microsoft Great Plains and apply each newly released service pack

mediaimage
Another scenario is more conservative – upgrade is investment plus it forces MRP users to work extra hours to help consultants with pre- and post- upgrade testing – such as printing major reports and verifying balances.  This second conservative approach recommends jump over one version,Microsoft Dynamics GP Great Plains Upgrade FAQ Articles i.e. if you are on version 7.0, you don’t upgrade to 8.0 but instead wait version 9.0; plus you upgrade to new version only when it is “tested” in large number of upgrades (in the first 6 month after being released).  Additional upgrade considerations should be given to custom modules, reporting, in-house-made integration, EDI, etc.  Let’s come through version update checklist:• Reg Key.  It is ERP industry standard service practice, when vendor requires all the customers to be in annual enhancement program, which requires you to pay annual fee.  If you lapse in the annual enhancement program, you should expect certain penalty to pay in order to get reenrolled into the enhancement program.  When you are current in enhancement, you receive reg key for the new version automatically• Upgrade Technology.  In the case of Great Plains, assuming that you are on SQL Server platform – upgrade is automatic process, built into GP utilities.  When you first install new version on the server – you will get a message about new version upgrade – and utilities will launch the upgrade itself upon your authorization.  There are multiple upgrade scenarios and “what ifs”, this is why it is not recommended for end user to do it; however it is theoretically possible to upgrade on your own – be sure you have full backup for SQL and your GP workstations (plus Server side software) to be able to roll back.  GP has internal architecture, known as Microsoft Dexterity – this architecture drives upgrade process and deploys it own tools to do so.  You should be familiar with such GP Dexterity features and terminologies as Dynamics.dic, Dynamics.set, Reports,dic, DEX_ROW_ID• Reports Upgrade.  There are several types of reports: ReportWriter (SOP Long Invoice Form is one of the most popular modified reports), SQL Server Reporting Services or SRS and Crystal Reports.  The last two reporting technologies are pretty version independent and typically upgrade without problem• Dexterity Upgrade.  This is one of the most popular GP customization technologies.  If you need to upgrade dex modifications, you need to have dexterity custom dictionary with customization source code scripts.  In most of the cases developers give you Dynamics.dic with your custom logic, in some cases Extract.dic