Microsoft Dynamics GP is new name for former Great Plains Software Dynamics and eEnterprise ERP applications. The inheritance is pretty obvious and it is in Great Plains Dexterity platform.
Great Plains Integration Manager module should be considered the first choice in integration projects, including historical data conversion, beginning balances import and even ongoing GL transaction integration, if Great Plains is used on General Ledger level only (like if you have external Payroll service and receive pay period GL transaction from Payroll outsourcer). The second pick in integrations, and in essence it might be your first choice if you prefer add-hoc programming in C#, VB and SQL with XML comfort level – is eConnect SDK. The third and pretty non safe method is direct SQL scripting with insert statement and SQL stored procedures:
1. Dynamics GP Integration Manager. If you got historical negative experience with this tool, when you were on legacy versions: 7.5, 7.0, 6.0, 5.5, 5.0, 4.0, then please know that in those good old days IM was based on OLE technology, deploying Great Plains user workstation as OLE server – this method dictated poor performance, as every integrated transaction would go through user key entry imitation in OLE server. With GP version 10.0 Integration Manager is in large degree rewritten in eConnect platform, where performance is breaking through as eConnect technology layer is encrypted SQL stored procedures, imitating GP Dex logic. If you can import your text legacy data export files into SQL Server custom tables, then consider creating SQL custom views and build Advanced Query in IM to deploy these views – then performance of IM eConnect connectors will be astonishing. In order eConnect to manage huge number of records, you should increase number of pools in eConnect COM+ object settings
2. eConnect direct programming. If you are experienced programmer in C# or VB, then you should find plenty of useful examples in eConnect SDK. eConnect integration programming is in our opinion simpler than Microsoft Dexterity sanscript programming and allows you to debug your software development code in Microsoft Visual Studio
3. SQL Scripting Integration. It might be a temptation to access and change Great Plains table records in SQL Query Analyzer, we strictly discourage you to do so. Great Plains Dynamics GP, in contrast to such ERP applications as SQP Business One, doesn’t isolate you from direct SQL access, however direct data change in GP should be trusted to certified Great Plains Technical Consultant
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
