Microsoft Great Plains Dexterity Customization Projects overview

May 13

08:47

2007

Andrew Karasev

If you deploy Microsoft Dynamics GP Great Plains as your ERP system and need application logic to be modified – this may include however not limited to legacy system integrations, industrial reporting, new data entry logic, GP Sales module web exposure. GP is written in Microsoft Dexterity and one of the customization tools you may consider to deploy is Dexterity.

Other tools are eConnect, SQL stored procedures, VBA/Modifier, Integration Manager with VBA scripting and data translation. In this small article we review Microsoft Dexterity:

Modification Capability. Dexterity can modify virtually everything in GP. It by its architecture seamlessly fits into GP security model. Dex exposes to developer all GP forms and windows, allows to alter GP logic by placing triggers, which will run prior or after original object logic. In Dexterity you can manipulate such external custom applications as COM object – this will open web services World to dex developer
OOP. As Dexterity was designed in earlier 1990th – it is not Object Oriented in modern sense of its concept. It may mean that Dex development will take longer and will require good QA
Customization Upgrade. If you have DYNAMICS.DIC file with your historical customization, then we can upgrade your custom logic to newer GP version
Customization Revision. When we do upgrade of your dex legacy customization, we typically advise you to deploy new tools and move portion of old dex custom logic to such technologies as SQL scripting and eConnect

Article "tagged" as: