If you have Microsoft Dynamics GP implemented in your organization and you are currently on one of the older versions: 8.0, 7.5, 7.0, 6.0, 5.5, 5.0 4.0, older versions often come with Pervasive SQL and Ctree databases, or even archaic Great Plains Accounting for DOS 9.5, 9.2 or 9.0
you may have a reasonable question – why you would need to upgrade Dynamics GP to current version? In this small publication we would like to give you typical answer and technology highlights:
1. Computer platform obsolescence. This is the biggest concern, when you are on the version, which is 10 years old or even older than that – GPA for DOS is good example. Great Plains Accounting was dedicated for Microsoft Windows NT 4.0 Server and old Btrieve. There is the trick to move it to Windows 2003 Server on Pervasive SQL 2000 DB – but nobody would guarantee that it will be 100 percent compatible
2. Business Portal. Great Plains BP became strong and popular with recent Dynamics GP versions: 9.0 and especially 10.0. In GP Business Portal the most popular modules are: Electronic Document Delivery, HR and Employee Self Service, Requisition Management, Order Management with catalogues. Business Portal is Sharepoint web based application, and BP user license is cheaper than regular GP user (around $40 per user)
3. eConnect. For earlier versions of Great Plains Dynamics and eEnterprise you had Great Plains Dexterity as popular customization and integration tool. However Dex is proprietary and not easy to acquire for generic software programmers. eConnect was introduced for ecommerce developers and we personally think that eConnect became ready for production deployment with version 9.0. With Great Plains Dynamics GP 10.0 eConnect installs automatically and you can use eConnect runtime for your Microsoft Visual Studio C# or VB.Net development projects
4. Client Installation Package and Publishing Automatic Updates. In the past you have to deploy each GP workstation individually, following strict installation procedure. With GP 9.0 and 10.0 you can create so-called Client Installation Package, where you can even force GP Reports, Forms, OLE Notes and Letters (collection for example) to be stored centrally on the UNC path. Plus you can force automatic updates, such as chink CNK files (Dexterity add-ons) and GP Service Packs (MSP files)
5. SQL Server Reporting Services predefined reports for Dynamics GP. In the past, Great Plains recommended Crystal Reports, where you had to purchase CR design license. With SSRS you are getting web based reporting tool free
6. There are other advantages, such as Great Plains Workflow, Web Services for Great Plains, non-for profit modules
Dexterity Customization for Dynamics GP Evaluation Level Paper
When you are developer it is always a good idea to read technical manuals. But if you was just assigned to the IT team to decide if Dexterity is the right tool to customize your ERP application then first you need something which is in style of ‘easy reading papers’ or FAQ
Planning Dynamics GP Customization in Large Corporation
If you are reading this page then chances are high that you were not able to find ISV add-on and need customization project. Let’s talk about planning, quality assurance and future event such as version updates.
Dynamics GP Invoice Logo Attributed to Specific Company or Crossing the Borders of Three SOP Forms
Initial Great Plains Dynamics architecture had three SOP Invoice forms: Long, Short and Blank. Modern GP is popular in scenarios where you have more than three companies under one business entity umbrella
