If you purchased and implemented Great Plains Software Dynamics, Dynamics C/S+ or eEnterprise in the middle of 1990th and came through several upgrade cycles, you may probably reserve the tough question: why Great Plains Upgrade is so difficult, unpredictable, over budgeting and consulting time consuming? Why it is so smooth if you are on PeachTree or QuickBooks?
The answer is in scalability of Great Plains Dynamics GP. Great Plains Dynamics or current Microsoft Dynamics GP ERP was always based on open DB platforms, such as Microsoft SQL Server 6.5, 7.0, 2000, 2005, 2008, Pervasive SQL 2000, Btrieve, Ctree. Small Business Accounting packages are typically based on their proprietary DB platforms (where accounting application vendor doesn’t have to pay for new installation and all the software purchase money comes to the small business ERP publisher), Scalability translates into synchronization between Dynamics GP Workstation, Server, SQL Server, FRx reporter, SSRS (SQL Server Reporting Services). In this small publication we would like to give you IT VP or Executive overview:
1. Vulnerable to Update Great Plains versions. In our opinion these are Great Plains 5.5, 6.0 and 7.0. And again to our personal opinion, these versions were released in the Clinton era of IT and High-tech booming, probably a bit premature
2. Upgrading to Dynamics GP 10.0. Here we see different trend in upgrade issues nature. Great Plains 10.0 is tightly integrated with Sharepoint (SSRS), Microsoft Office: Outlook, Excel and Word. Plus, Dynamics GP Microsoft subdivision changed Security model of Great Plains: if you are upgrading from Version 9.0 to 10.0 it is highly recommended, that you take Great Plains 10.0 Security training class or invite Great Plains VAR, who is familiar with 10.0 Security model to do upgrade and post-upgrade user training
3. Switching from Pervasive SQL 2000, Great Plains Accounting for DOS and Windows and Mac. There is Migration tool to move you from GP for Ctree or Pervasive/Btrieve. If you are GPA for DOS, you can ask for migrating you to Dynamics GP 7.5, or 9.0 on MS SQL Server 2000 or 2005
4. Dexterity Customizations. In 1990th Great Plains Dexterity was oriented to Btrieve and Ctree customers, for whom Transact SQL statements were not an options, and instead Dex offered Dexterity cursors. This logic is slower, comparing to modern days SQL Server. If you have old Microsoft Dexterity customization dictionaries, please consider to review the code by professional GP Dexterity Programmer
5. If you cannot afford Great Plains Upgrade at the time of recession. In our opinion your option is to switch to the Great Plains Reseller and Technology Partner who is committed to Great Plains Remote Support and is in the industry for ten years plus. In this case you won’t have to pay for new Great Plains Consultants learning curve. If you are on Great Plains Accounting or GPA for DOS, please consider moving GPA server to Windows 2003 on Pervasive SQL 2000 SP3. This step will allow you to break through WindowsNT 4.0 or Novell hardware limits and failures. In the future you could enjoy discounted price to be upgraded to Dynamics GP business ready licensing
6. eConnect integrations. We prefer to recommend you to implement Microsoft CRM, from where you could integrate your master records and transactions to Great Plains through eConnect SDK programming
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
