At some point in your Dynamics GP customization development career, you may come across the dag.exe command needed to generate the Application.Dynamics.ModifiedForms.dll. This .dll comes in handy when writing GP add-in’s for modified forms. However, you may run into issues when trying to run the dag command for the first time. The following troubleshooting steps and considerations have helped me get the dag.exe to run properly on most occasions:
- Do you have access to both the dag.exe file and the Dynamics.set file? If not, not being able to run the dag command properly may be an access issue.
- Does your dag.exe command look like: dag.exe 0 “c:\Program Files\Microsoft Dynamics\GP\Dynamics.set” /F /N:Dynamics. The first time I tried to run the dag.exe, I did a quick search online and came across something like the command shown above. Chances are running this will not work. The path enclosed in the quotes should be the path to where your Dynamics.set file is, so update that portion of the command accordingly. Also, in the command prompt, be sure to change the directory (“cd”) to the dag.exe’s directory.
- If you run into problems up to this point, try moving the dag.exe file from its default “GP [GP Version] VS Tools SDK” directory to where the Dynamics.set file’s directory. Then change the directory (“cd”) in the command prompt to this new location and run the dag command.
- If the Application.Dynamics.ModifiedForms.dll already exists, there will be a message that indicates such. The file will have to be removed in order to run the dag.exe. Consider whether a new ModifiedForms.dll needs to be created and take precautionary steps, such as backing up the ModifiedForms.dll, before deleting the .dll.
This article was written by Kevin Huynh, Dynamics GP Technical Consultant for Tridea Partners. Tridea is a leading Microsoft Dynamics provider.