Microsoft Dynamics GP customizations could be developed in various tools: Great Plains Dexterity, SQL Stored Procedures, eConnect, Extender, etc. Traditionally, add-ons were written in Great Plains Dexterity, this architecture allows you to package Dex custom module into so-called Chunk file, which should be copied into Dynamics GP directory and when you launch GP workstation next time, you will get prompt to integrate new functionality
This integration converts chunk file into new custom add-ons Dictionary, registered in Dynamics.set file. This small publication is dedicated to IT manager level highlights on Dexterity technology and where you should consider Dexterity programming work for your organization:
1. Historical excurse on Great Plains Dexterity. Dex was coded in C programming language as the shell with its own architecture and scripting language Sanscript plus with its own instruments to manage Database access: table creation, records addition, deletion, update. For DB access Dexterity deploys cursors and this makes it a bit slower, comparing to direct aggregation in SQL language: Select, Insert, Update. Dex can, however call native Microsoft SQL Stored procedures, where you could dramatically improve Dex performance, in fact Microsoft Business Solutions ported good portion of former Dexterity cursors into SQL Stored Procs. Initially, introducing Dexterity Great Plains Software planned to have it as secured shell to avoid single DB platform dependency, but when Microsoft acquired GPS, this caution was obviously disregarded, as Great Plains ERP became since then committed to Microsoft Windows and MS SQL Server Platform
2. Where Dex might be not the best customization tool? The answer is simple – in integrations. If all you need to do is Dynamics GP integration – in eCommerce, EDI, Barcoding, with Legacy Systems, Lotus Notes, Excel, ODBC data source (Oracle, MySQL/PHP, Pervasive SQL, Ctree, MS Access) – these integrations do not need Dexterity, you can rather deploy either eConnect programming in C#, VB.Net, or even GP Integration Manager
3. Where Dex does its best job? In seamlessly integrated to Dynamics GP user interface custom screens, and especially when you need GP security real to be extended to these custom windows
4. How to locate Dynamics GP ISV Partner. Typically, ISV should not be local by requirements or company IT policies. Microsoft Dynamics GP Dexterity Software Development Factory is not a simple thing to launch and afford to maintain for typical local or even regional Great Plains Reseller
5. Feel free to call us: 1-866-528-0577, help@albaspectrum.com, we specialize in Great Plains Customizations, Integrations, Reporting, EDI, eCommerce
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
