There are times when you will need to install Dynamics GP from the DVD and you do not have the service pack that is running in your GP SQL instance. When you go to Customer Source or Partner Source to…

The Dexterity Integration tools include several object triggers. These triggers allow Dynamics GP to respond to certain events that occur within the application. The Dexterity triggers reside in the developer’s custom data dictionary. The trigger must be registered with the…

A Dexterity developer may need to create a customization to retrieve data from a non-Dynamics GP server. In this example, we will retrieve the next vendor ID from a server where Dynamics GP is not installed. A new push button…

Since most users look up vendors by vendor name, you can make the Dynamics GP’s Vendor Lookup window sort by the vendor’s name when the window opens using the Modifier with VBA tool. This tool may be active based on…

When using the Integration Manager, you may need to combine several files to create one source file. You can use the “Before Integration” script feature to accomplish this. To access the “Before Integration” script, double-click on the integration’s name and…

A Dexterity developer may need to create a customization to import data from a text file into Dynamics GP. These text files are generally used for input from Microsoft Excel or legacy applications. The following is an example of how…

At some point, a Dexterity developer needs to create a customization to export data from Dynamics GP into a text file, which is generally used for input to applications such as Microsoft Excel or legacy applications. The following example of…

Most developers familiar with Dexterity have interacted with third-party forms, part of the data dictionary for third-party products like Mekorma MICR, Binary Stream Multi Entity Management (Multi Facility Processing) or Ethotech Commission Plan. A developer may have to interact with…