Microsoft Dynamics GP ERP or former name Great Plains Dynamics and eEnterprise was originally written in specially created programming shell: Great Plains Software Dexterity.
Dex in turn is written in C programming language, providing certain level of computer platform independence in 1990th, where this question was actual for Great Plains Software position on the MRP software applications market. Dexterity architecture, especially considering current versions: 10.0, 9.0, 8.0 works on Microsoft SQL Server platform through ODBC connection and in this small publication we would like to give you initial highlights on Great Plains troubleshooting:
1. “Good” and “Bad” Great Plains workstation. If you are experiencing error message in Great Plains, please try to calm down and analyze – is it happening on all workstations or just on one of them? If the answer is – only on single workstation, try to review its peculiarity. Log in GP, on the top-right corner click help icon and write down the Version of Great Plains, something like 10.00.0903 (this is Great Plains Dynamics GP Service Pack 1 for example). Compare this number with Good workstation. If the number is not the same – likely that Service Pack version is causing the problem. The simplest way to fix SP issue is either apply appropriate service pack or copy GP folder from Good workstation to the one where you have the problem
2. Dex.Ini file. This file has settings for your Great Plains user workstation Dexterity engine. Dexterity is obviously the player, where Dynamics GP faces all software related error messages at the first place: DLL, Windows and Great Plains Service Packs, SQL Native drivers, ODBC settings, corrupt REPORTS.DIC, DYNAMICS.DIC and other Dexterity dictionaries to name few examples for you. In order to understand the sequence of events, you should enable logging in Dexterity. Please change the following settings in Dex.ini file SQLLogSQLStmt=FALSE to TRUE, SQLLogODBCMessages=FALSE to TRUE and SQLLogAllODBCMessages=FALSE to TRUE. If you do so, Dexterity will create DynSQL.log file (for version 10.0 in Data subfolder, in earlier versions in GP folder)
3. Great Plains ReportWriter issues. Corrupt reports are common in the scenario when you are modifying reports in the shared REPORTS.DIC file either by exporting and importing customization packages or by doing direct changes in Dynamics GP Report Writer. The fix is also very simple – either restore REPORTS.DIC from backup or export reports in RW from “corrupt” REPORTS.DIC, then delete this dictionary and re-import reports
4. Great Plains Dexterity Customizations. If you already tried DexSQL.Log file method and it didn’t help your Dexterity programmers to fix the problem, consider the step of installing Microsoft Dexterity on one of your computers and have your Dex developers to debug it
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
