Editing A Dynamics.set file

How Can We Help?

You are here:
< Back

Each line in the Dynamics.set (also called a launch file) contains information necessary for the GP runtime engine (Dynamics.exe or DPS.exe) to run the various dictionaries that make up a complete Dynamics GP application. When you install one or more integrating ISV applications, you add additional information to the launch file that allows the additional dictionary to work in the multi-dictionary environment.  Although the GP runtime engine normally automatically handles updates to the launch file, there are times that you might need to manually edit them.  Launch files can be edited with Notepad.

Although this is not a launch file that you would ever see or use, for illustration purposes the following shows how you would configure a launch file to launch Microsoft Dynamics GP, Advanced Intercompany (AIT) and Analytical Accounting (AA):

Microsoft Dynamics GP
Advanced Intercompany
Analytical Accounting
:C:Dynamics GP/Dynamics.dic
:C:Dynamics GP/Data/Forms.dic
:C:Dynamics GP/Data/Reports.dic
:C:Dynamics GP/IC.dic
:C:Dynamics GP/Data/ICFORMS.DIC
:C:Dynamics GP/Data/ICRPTS.DIC
:C:Dynamics GP/AA.dic
:C:Dynamics GP/Data/AA3180F.DIC
:C:Dynamics GP/Data/AA3180R.DIC

The first line (the 3) indicates the number of products included in the launch file.

The second section (product list) is a paired list of product ids (the numbers) followed by the name of the application.  Each application accounted for in the first line will have two lines.

Following the product list section, is a line that will always have Windows.  This value will match the WORKSTATION= line in the dex.ini file found in the \Dynamics GP\data folder. Do not edit these values in either file.

The final section (dictionary list) contains a trio of lines indicating the location of all dictionaries associated with the applications in the product list section.  All product dictionary trios must have unique dictionary file names.  File paths can point to either the folder in which Dynamics GP is installed or to a network share, but if you install applications on the workstation, the first line of each product trio must point to the same folder in which as the GP runtime engine is installed.  If the file path points to a network share and an ISV update includes a new .cnk file, the GP runtime engine will not properly update or create a new .dic file.

The order of these products can have an impact on your Dynamics GP system.  If you change the order of these applications, always move both the product list section pair and also move the trio in the dictionary list section.  The order in the product list section determines the order in which the GP runtime engine fires triggers.  If two different ISV applications trigger, for example, on a ‘Save Button’, the GP runtime engine will fire the first product’s trigger. If that product’s trigger does not have a ‘reject script’ process, the second product’s trigger will fire, but the first product has the ability to stop all other triggers from firing.