More articles are published about Microsoft Great Plains Dynamics GP 10.0. Very hot topic is eCommerce and web site design, development and support with integration to Great Plains via eConnect or custom SQL stored procedures and triggers. E-Commerce sites may have legacy trace and so be developed in the past in various technologies, including non-Microsoft: Java, JSP, ASP, ASPX, PHP, Oracle, IBM DB 2, etc
When we are talking about Microsoft Dynamics GP version 10.0, 9.0, 8.0, 7.5, 7.0, 6.0 or 5.5 we mean such ecommerce integration technologies as eConnect (10, 9 and 7.5) and SQL stored procedures (for earlier Great Plains Dynamics/eEnterprise versions). If you still deploy legacy Pervasive SQL 2000/Btrieve or Ctree/Faircom versions of GP, this is 7.5 and earlier – ecommerce can still be tailored to your legacy ERp, however we recommend you to upgrade to GP 9.0 or 10.0. Some technology and programming highlights:
1. eConnect and Posting Server. Posting Server is extension to eConnect, allowing you to post GP batches, while eConnect has the option to create work transactions and place them into GP batch in the case of ecommerce – more likely you are interested in Sales Order Processing module (SOP)
2. ASPX .Net development. If you start from scratch or modify existing .Net e-commerce website, your choice is simple - .Net ASPX. Back end is probably SQL Server, assuming that you may need custom databases, aside from such GP database as DYNAMICS and company databases
3. Visual Studio .Net C# or VB development. If you are VS .Net developer you can create and debug GP eCommerce integration project. However, you should expect some technical challenges, especially when going deep to GP business logic imitation. We recommend you to combine Microsoft Dynamics GP Dexterity customization with your .Net C# project to make your job done
4. eCommerce upgrade and redeployment. If you think that you should switch away from non-Microsoft platform to .Net, then you should invest your time in such SDK as eConnect, initially designed for eCommerce developers to hook Great Plains as back office ERP
5. Great Plains Integration manager. This GP module allows you to do ongoing integrations to GP back office. In the past it was mostly end user tool. Nowadays when IM is in process of being rewritten in eConnect, integration performance issues are to be resolved and IM is promoted as excellent development instrument. From legacy IM side you can easily modify it via VBA scripting. In connection to ecommerce website, IM can be scheduled for GP backoffice MRP update
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
