URGENT: Applying 2008 Year End updates for Microsoft Dynamics GP 9.0 and 10.0


Many GP administrators and partners have been experiencing issues after applying the Year End updates. These issues may range from corrupted reports dictionaries, apparent posting errors, and system crashes.

My 2 cents on the issue and how to prevent them from happenning: since these Year End updates are inclusive of service pack 4 and Service Pack 3 for Dynamics GP 9.0 and Dynamics GP 10.0, respectively, you must follow all procedures outlined for a service pack installation, especially as it concerns modified reports and modified forms for Dynamics GP and third party products:

1) MAKE SURE TO EXPORT ALL CUSTOMIZATIONS (Forms, Reports, VBA Customizations, References) TO A PACKAGE FILE (.Package), UNDER TOOLS > CUSTOMIZE > CUSTOMIZATION MAINTENANCE IN GP 9.0 AND MICROSOFT DYNAMICS GP > TOOLS > CUSTOMIZE > CUSTOMIZATION MAINTENANCE IN GP 10.0.

2) REMOVE ALL EXISTING MODIFIED REPORTS DICTIONARIES AND MODIFIED FORMS DICTIONARIES FROM THEIR CURRENT LOCATION. TO BE ON THE SAFE SIDE, MOVE THESE DICTIONARIES TO ANOTHER LOCATION ON OR OFF YOUR SERVER.

3) BACKUP DYNAMICS AND ALL COMPANY DATABASES PRIORT TO APPLYING THE YEAR END UPDATE PATCH. STORE THESE BACKUPS IN A QUICKLY ACCESSIBLE LOCATION.

4) APPLY THE YEAR END UPDATE PATCHES FOLLOWING ALL INSTRUCTIONS OUTLINED BY THE INSTALLATION NOTES AND RUN DYNAMICS UTILITIES TO PERFORM ANY UPDATE AND VERIFY ALL DATABASES.

5) REIMPORT ALL YOUR CUSTOMIZATIONS FROM THE PACKAGE FILE EXPORTED IN STEP 1.

Until next post!

MG.-
Mariano Gomez, MVP
Maximum Global Business, LLC
http://www.maximumglobalbusiness.com/

Comments

Post a Comment

Popular posts from this blog

DBMS: 12 Microsoft Dynamics GP: 0 error when updating to Microsoft Dynamics GP 2013 R2

Image
Hello all! It's been quite a while since I've actually written anything of remote interest to anyone who follows my blog, but at the same time, you will be pleased to know that I've been quite busy in the consulting front, with upgrades, server migrations, complex multi-instance postings involving 10's of thousands of transactions, wrapping up some Field Service Automation projects, and the list goes on and on. This time around I want to bring to the forefront, an issue I encountered updating  from Microsoft Dynamics GP 2013 SP2 to Microsoft Dynamics GP 2013 R2 plus the latest service pack. Background My client requested a server migration to a new environment where they wanted to deploy Dynamics GP 2013 R2 web client (plus the latest service pack) and upgrade their relational database management system to Microsoft SQL Server 2014. This is something I'm absolutely comfortable with (for the most part) given also that my client was sitting at Microsoft Dynamics...
Read more

Do I have to use those "Z-" currency IDs in GP?

Image
I know this seems like a trivia question, but recently I have come across a number of clients who have been using Microsoft Dynamics GP for a number of years and have been told by their former partners that they *must* use the predefined currency IDs created after adding the sample company, with no real explanation to support these claims. Case in point, my new client in Saudi Arabia, has been struggling for years to understand why they were told to prefix all currency IDs with the "Z-". So they went ahead and setup "Z-SR" for the Saudi Real. If you are familiar with Microsoft Dynamics GP and the sample company, Fabrikam, you may have noticed by now that after adding the sample company (which is not a requirement by any means), you will get a number of predefined currencies such as Z-US$ (US Dollars), Z-UK (British Pounds), Z-C$ (Canadian Dollars), Z-AUD (Australian Dollars), and so forth, accompanied by a number of exchange rate tables. If you are not familiar wi...
Read more

Microsoft Dynamics GP Scrolling Windows and Line Sequence Numbers

Image
I thought I would write about something meaningless that no one really thinks about. However, I realized that this is a compelling topic since it makes for some interesting discussion around the ability to insert line items withinin most transaction scrolling windows. Let’s take some time to understand where Line Sequence Numbers come from. A Line Sequence Number is auto generated by Dynamics GP and uses a seed value of 16,384 as a basis for the first line. Each subsequent line in the scrolling window is incremented by this number, so line number 2 would have a Line Sequence Number value of 32,768, line number 3 would have Line Sequence Number Value of 49,152, and so on. Since most GP transaction entry scrolling windows allow inserting rows in between line items, the newly inserted Line Sequence Number value is calculated as an average between the previous and the next line item sequences, i.e., if you were to insert an item in between row 1 and row 2 in the scrolling window -- keep in...
Read more