Microsoft Dynamics GP, formerly known as Great Plains Dynamics or eEnterprise, as other ERP and mid-market MRP applications has its own settings file.
As it historically was coded in Great Plains Dexterity, this file is Dex.ini. This file could be found in Dynamics GP workstation directory for versions 9.0, 8.0, 7.5, 7.0, 6.0, 5.5, 4.0 and earlier, if you are on GP 10.0, then it should sit in Data subdirectory. In this small publication we would like to come through some of its settings and flags:
1. If you need to resynchronize Dynamics.dic file to its account structures, especially if you believe that your Dynamics.dic file was corrupt and you copied it one more time from GP CD #1. Change Synchronize to True and Initial to True. This will force Dynamics on the first user login to switch to Utilities and synchronize the dictionary, which is your Dynamics.dic – metadata and business logic file
2. Logging Dexterity, SQL and ODBC traces. This step is needed, when you sort of giving up in getting unknown error message in Great Plains. Assuming that you already did the research trying to find something about it in Microsoft Dynamics GP Customer Source. Even if you do not have support plan with Microsoft, you still can get reasonable explanation on what is going on and probably the idea on where the fix could be. Please make this changes in Dex.ini: SQLLogSQLStmt=TRUE
SQLLogODBCMessages=TRUE
SQLLogAllODBCMessages=TRUE
Then find Dex.log file in the same directory, where Dex.ini is located. We recommend you to make a copy of this file right after the moment when your error message triggers, and then review it with creativity of software programmer. More likely you will have the idea on what went wrong
3. GP Integration Manager Path. Here you typically have to fix this line: IMPath=. When you install IM, it tries to link installation to your local Great Plains workstation, however, there are known issues on Terminal Server/Ctrix and even fat GP clients. Please do not try to fix FRx client path in Dex.ini. Instead, find FRXDYN.ini file and change path there accordingly
4. Great Plains Dynamics legacy Dex.ini settings. Here you should know about location and locations translation theory in old Great Plains on Pervasive SQL (former Btrieve), or Ctree. The lines to review are: Workstation=WINDOWS – here WINDOWS with uppercases is the location ID to use for this specific GP workstation.
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
