Sunday, August 19, 2012

Microsoft Dynamics GP Great Plains Upgrade to Version 10 - Overview


If you are Great Plains customer and deploy GP ERP in your organization as accounting backoffice, you probably remember that the update to version 7.5, after 8.0 was very fast and painless. Upgrading to version 9.0 Great Plains was relatively simple, but its role in the update wizard was increased and if you are great Plains Consultant, you kind of feel that you have lost control over the update process first. Well, the upgrade to Microsoft Dynamics GP version 10.0 is more complex, with multiple defects. If you plan to upgrade to version 10, we would like to share with you our experience:

1. 64-bit dilemma. eConnect workstation portion at this time, in November 2007 is not supported on 64-bit Windows, including Vista 64. Even Sysdata FRx folder must reside on 32-bit version as well. This 64-bit computing arm seems to be quite a problem for producers of software: new laptop and desktop computers now come with Vista 32-bit or 32-bit Windows XP. Microsoft SQL Server 2005 seems to be comfortable in Windows Server 2003 64 bit, but when we come to the workstation side MS NET and COM + objects (WS part of eConnect and eConnect Runtime) -. The problem manifests itself. In addition, Microsoft Dynamics GP Business Portal is not supported (currently) 64-bit

2. New GP Security Architecture. GP security is redesigned and this is a good sign for ERP Security administrators are now able to create or use existing tasks (usually small) and roles (groups). Roles exist at the product level: Dynamics GP core DYNAMICS.DIC accounting, project accounting, fixed assets, etc. When something is revised and redesigned from scratch, you should expect some additional work to configure new components and use GP consultants time, however there was unexpected upgrade surprise, described in the next step

3. GP Security update failure. In manual update you are assured that every user will be translated into existing security roles and responsibilities of users (with user name in the roles and job descriptions, which is not the best thing to have, probably). However, even this bridge of security fails in the process of upgrade version. Microsoft has indicated that in order to obtain the transfer of security you must remove the spaces from the folder of Microsoft Dynamics GP workstation installed 10.0 (where the spaces are suggested by default install or upgrade wizard). We hope that with GP 10.0 Service Pack 1 of these annoying problems will be solved, but for now, please be aware and try to expect and deal with problems

4. Other known issues: SY02700 table, this is in the Dynamics database, the problems we have heard reports this error when updating a table update

5. Update order purchase processing seems to be fixed: POP line work and historical tables were known to be the creators problem in upgrading to GP 9.0. With version 10.0 of the problem seems to be rectified

6. Integration Manager IM.MDB update problem. If you are upgrading from GP 7.5 to 10, then we know about update errors, where they are converted Query query and reporting, but the destinations and destinations mappings are not

7. Service Pack 1 on hold recommendation. We are optimistic for the maintenance of our nature, however, you should decide the level of acceptable risk. Also, if you are on GP 9.0 with Service Pack 3 applied, you can not upgrade to 10.0, up to the GP 10 SP1 is released

If you want our help Dynamics GP upgrade, free to call or e-mail ...

No comments:

Post a Comment