Microsoft Dexterity or former Great Plains Dexterity was designed in earlier 1990th with assumption that C programming language will provide computer platform independence: Microsoft Windows vs. Mac or Solaris/Unix, plus database independence or at least easy switch: Ctree, Pervasive SQL/Btrieve, MS SQL Server, Oracle, DBII, etc
Dexterity architecture was transferred to MS Visual C++ somewhere around 1999 with some additional bug fixing work, however pretty flawless. When Microsoft purchased Great Plains Software on the edge of XXI Century, the basis of Dexterity lost its actuality – in fact Microsoft Business Solutions actively moved toward phasing out all the other platforms, but MS SQL Server by introducing MSDE platform – free version of SQL Server, without some tools, however. Let’s look at MS Dexterity from this angle:
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 FAQPlanning 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