Ecommerce integration with Microsoft Dynamics GP is possible on various levels. If you are starting ecommerce project from the ground, you may look at packaged ecommerce products, available as custom add-ons to Dynamics GP.
However, and this is what we assume in this small publication, a lot of ecommerce businesses have their websites and the integration should be on the level of custom connectors: pushing new customers, new catalogs, new orders and probably payments to Great Plains. Please, consider these tools and solutions:
1. eConnect. It is set of stored procedures with interfaces for Microsoft Visual Studio ecommerce developer. If you have programmers in staff, you should review eConnect with them and decide on the integration specifications. One thing often comes to the question – eConnect doesn’t have functionality to post Great Plains batches, in order to post Dynamics GP batches directly from ecommerce portal, you should consider deployment of Alba Spectrum Posting Server
2. Order Connector. This product is supported by Alba Spectrum. It allows you to deploy simple ecommerce integration logic to Great Plains Sales Order Processing module. If this is your case, Order Connector allows you to call its stored procedures directly, which might give certain performance gain over eConnect and you do not have to learn eConnect. For small Great Plains Dynamics customers, who are on older GP versions: 8.0, 7.5 – you could also use Order Connector, and eConnect for those versions was in introduction phase
3. Integration Manager. IM allows you to setup integration on the GP user level with some custom tweaks: VBA scripts. It should solve your ecommerce integration needs, if real time integration is not required – you can either have GP user to call integration on demand or schedule IM via Windows macro routines (out of scope for this article)
4. Direct SQL Custom Stored Procedures. This approach may look natural for SQL programmer, however in this scenario you will need to replicate GP business logic in your scripts. Just consider the fact, that eConnect already did exactly this – it replicated Great Plains Dexterity code in encrypted SQL Stored Procedures, so maybe you should consider more efficient programming time spending simply by deploying eConnect instead. However, this is possible approach and theoretically you can replicate data feeding to Dynamics GP tables as if it is done via user interface
5. If you have further questions or concerns, please feel free to call us: 1-866-528-0577, help@albaspectrum.com
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
