| Nowadays Microsoft Great Plains or any other ERP | | | | to locate Dex developer, especially the one who has |
| application should be rather considered as the platform | | | | access to Dexterity source code |
| for integration of your peripheral applications: CRM, | | | | 2. eConnect. This SDK was specially created for |
| eCommerce, Custom Sales Order Processing, EDI | | | | e-commerce developers to enable GP backoffice |
| (Electronic Document Interchange) and others. Plus | | | | integration for eCommerce web sites. Since the initial |
| of-the-shelf available business logic often requires | | | | version back in earlier 2000th, eConnect covered more |
| customization, where you got to select appropriate | | | | GP modules and business objects: SOP, POP, Project |
| software development tools to do the job. Since the | | | | Accounting, General Ledger, Receivable Management, |
| time of Great Plains Software being purchased by | | | | Payables Management modules. The core of |
| Microsoft, Great Plains was under the way of being | | | | eConnect are encrypted SQL stored procedures |
| redesigned to be tightly integrated with .Net and | | | | 3. GP Integration Manager. If you review GP IM 10.0, |
| Microsoft Outlook and Office stack of products. Let's | | | | you will see that IM connectors are now available in |
| take a look at the GP technical layer: | | | | most of the business logic cases in eConnect. |
| 1. Microsoft Dynamics GP Dexterity architecture. Great | | | | EConnect connectors drastically improve IM |
| Plains Dex was designed to serve as Great Plains | | | | performance and doesn't require GP workstation |
| Dynamics platform in earlier 1990th, when similar | | | | running on the same computer (old IM connectors |
| approaches were taken by SAP - ABAP and | | | | were using GP workstation as OLE server) |
| Navision - C/SIDE. Dexterity is in turn written in C++ | | | | 4. SQL Scripting and Stored Procedures. If |
| programming language. To give you Dex architecture | | | | performance is the imperative, then you should |
| surface signs: DYNAMICS.DIC, DEX.INI files, | | | | consider SQL scripting, which will allow you to create |
| DEX_ROW_ID that you see in each GP table. If you | | | | primitive business logic, where you don't need complete |
| plan to use Dexterity for customization, then you need | | | | business logic validation, made by eConnect. |