In the realm of mid-market Corporate ERP, MRP, or Accounting applications, technical support is a critical aspect that can often be managed in-house, saving on costly consultant fees. This article delves into the common issues faced by users of Dynamics GP, Great Plains Dynamics, and Great Plains Accounting (GPA) for DOS and Windows, and provides guidance on how to address these challenges before reaching out to a Great Plains Consultant.
Before you consider hiring a consultant, it's worth exploring the Dynamics GP Knowledge Base. Surprisingly, over half of Dynamics GP customers with an active annual enhancement contract with Microsoft Business Solutions bypass this resource and directly contact their Dynamics GP Partner, incurring unnecessary expenses. The Knowledge Base is a free tool for those with an active support contract, which is typically included for the first year after purchasing Dynamics GP licenses. However, if you find yourself without a contract and blocked from Customer Source, don't despair—there are still steps you can take to resolve your issues.
One frequent problem is batch posting limbo, where a batch fails to post completely and remains locked in a posting status. For versions GP 7.5 and newer, a batch recovery mechanism prompts you to reset the batch posting status. However, if transaction editing is required, you'll need to manually verify each document's GL distribution.
GPA, particularly the DOS version, often encounters Btrieve-related errors. Familiarizing yourself with file rebuild utilities and exporting tables to text documents can help identify corrupt records. For GPA for Windows, adjusting Btrieve settings in the GPAWIN.INI file can improve performance.
For data repair on Pervasive SQL 2000, Btrieve, or Ctree platforms, Microsoft Access serves as a useful ODBC linking tool. Understanding the Great Plains table structure is crucial, which can be found under Tools -> Resource Descriptions -> Tables.
The Check Links utility can sometimes resolve data issues without the need for data repair via SQL Server Query designer or Microsoft Access, especially when using Pervasive SQL 2000/Btrieve.
When installing the client interface for newer versions like 9.0, 10.0, and 2010/11.0, it's essential to apply the same service pack as the production environment. For older versions, copying a working user workstation's setup can ensure compatibility.
If you're moving an old Pervasive SQL-based version, it must be deployed on a 32-bit Windows Server due to compatibility issues. For MS SQL Server-based versions, following detailed moving instructions from your Dynamics GP VAR or Microsoft Business Solutions is recommended.
To delete a user, ensure all users are logged off and remove the Activity.* file from the Dynamics\System folder on the server. For MS SQL Server, this can be controlled from the Query Analyzer.
Issues with FRx often relate to user profile changes. Verify the Sysdata location and ensure it matches with other FRx workstations. Keeping a backup of the Sysdata folder can prevent catalog corruption.
For Integration Manager, updating the path to the Integration database is necessary for new user installations. With eConnect, ensure that passwords are updated regularly to prevent access issues.
Version upgrades and custom programming should generally involve a Great Plains consultant due to the complexity and potential issues that may arise. For those who are comfortable with programming, tools like GP Dexterity, VBA with Modifier, and Extender can be used for customization.
Creating a user application with eConnect libraries allows for manipulation of Dynamics GP objects and documents, which is ideal for simple e-commerce custom application development.
When designing reports, it's best to use SQL Server Views or Stored Procedures to avoid data duplication and facilitate cross-database queries.
While many technical issues with Great Plains software can be resolved in-house, there are times when consulting a professional is necessary. If you require assistance, consider reaching out to a reputable support provider like MBS.
For further information on Dynamics GP and Great Plains, you can visit the official Microsoft Dynamics GP page or explore the Dynamics GP Community for additional support and resources.
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
