Microsoft Dynamics GP ERP, formerly known as Great Plains Dynamics, eEnterprise and in its earlier DOS version – Great Plains Accounting, is now available on Microsoft SQL Server platform early and only versions 10.0 and 9.0 are supported at this time.
Most of current Great Plains recovery requests are for MS SQL Server 2005/SQL Select and 2000/MSDE, however as earlier Great Plains Select was available on Pervasive SQL 2000/Btrieve and Ctree/Faircom – most sophisticated data recovery might be for these non Microsoft DB versions. Before you call your Great Plains Guru (expecting to pay for Great Plains Support), please read how you could try to recover Dynamics GP data on your own if you are SQL DBA, or IT support engineer, if this is about old Pervasive SQL files:
1. Try GP Check Links. Ask Dynamics GP users log off, Maintenance->Check Links, then select the series and tables clusters, where you suspect data integrity compromise. For example, Sales series and Sales Work cluster, if you expect data is corrupt in Work SOP documents. What Check Links does – it verifies tables business logic integrity and tries to add lost data or modify existing data, based on business logic metadata rules. One of the cautious about CL – if you have custom integration, please discuss with your Dynamics GP programmer or Great Plains ISV partner, if Check Links doesn’t harm integrated data
2. SQL Dynamics GP tables repair. First, you got to be very familiar with the tables and their relations, you can review GP tables architecture in Dynamics GP SDK, which could be installed from CD2, or for quick reference, Tools->Resource Description->Tables in GP user interface. Then, when you know what you are doing, we recommend you to back up the tables, which you plan to repair: select * into GL00100_Backup from GL00100 – this statement will create new tables and copy all the records from GL Account Master into it. If you repair fails, you can always roll back: alter table GL00100_Backup drop column DEX_ROW_ID and then you clear GL00100 table and insert into GL00100 select * from GL00100_Backup
3. Btrieve/Pervasive or Ctree data repair. Here you typically install ODBC driver from GP CD and create new Microsoft Access Database, where you link all or required tables from your Pervasive/Ctree. Before the repair, you make a backup of the whole company folder or copy and rename desired files. If Great Plains Dynamics is one of the legacy systems for you and you are SQL DBA, you can create linked server to Pervasive SQL or Ctree data from SQL Server Management Studio 2005 or Enterprise Manager 2000
4. Great Plains Accounting for DOS and Windows data repair. Here, you rather count on daily backup and simply restore all from it. If you are facing specific error message in GPA, you should call your Great Plains Consultant or feel free to contact us: 1-866-528-0577, help@albaspectrum.com
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
