Great Plains Software Dexterity platform was designed in earlier 1990th to be a foundation for Great Plains Dynamics and Dynamics S/C+. Dex was built on the principles of operating system “independence” (C programming language was in time believed to provide shell recompilation, including graphical components) and database platform independence
When Microsoft acquired Great Plains Software and formed ERP subdivision, Microsoft Business Solutions, these principles lost their initial focus, as you can suppose, Microsoft turned Great Plains to get advantages of Microsoft Windows OS source code and MS SQL Server as Microsoft database. Every action or decision obviously has pluses and minuses. Dex lost platform independence, but it gained the potential to increase its performance. Let’s take a look at these potentials closer:
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