Integration Anatomy.Sometimes we are trying to get the best products in integrating ecommerce shopping cart with your Corporate ERP application. Usually into SOP Sales Invoice (SOP10100 and SOP10200 tables) with Customer Deposit (in B2C case) or just without deposit (in B2B scenario, where you may sell on account). If you think Integration Manager doesn't fit and you need real time ecommerce shopping cart integration. As eConnect libraries could be included into MS Visual Studio web project, shopping cart integration could be triggered to happen immediately when the order is paid. And finally in the destination your design how the fields from the Queries will be mapped into destination document fields (with possible VBA script modification logic, data translation replacing one value or string with another, and other methods). It is recommended to have Great Plains technical or even functional consultant to help you with setup. If you would like to deploy eCommerce product and decided that neither Integration Manager, not eConnect, nor Order Connector do the job for you, we invite you to see the demo of Alba Spectrum eCommerce module for Dynamics GP Great Plains. If you plan to go and try advanced ODBC queries (directly pulling data from ODBC compliant database) then you should have experience with the DB platform (the most elegant and powerful way is to create SQL view and base the ODBC query on the view).
1. What kind of experience is required to setup IM Integration?
2. Where shopping cart goes in Great Plains?
3. Integration scheduling.
Ecommerce Shopping Cart platforms and integration to Great Plains.First one would be eConnect direct programming (you should be experienced in such Microsoft .Net programing languages as C# or VB where you will enjoy code samples, potentially also C ). Next, you choose the integration destination, such as SOP Entry for the recommended way to transform the cart into Sales Invoice. Sometimes, when you are selling service
free asp shopping cart with flat one line description it is more natural to send it as Accounts Receivable Invoice (RM10301). Not a problem, assuming that you have read the recommendations above and you still feel that they do not do the job or do not give you a way to follow. But, it might be much easier, if we just listening the stories of other ecommerce merchants and retailers. This method gives you flexibility and such great advantage, as preserving your historical ecommerce programming investment, as it doesn't require you to redeploy B2B or B2C ecommerce website on the new platform or product. We strongly believe that such popular carts, as Magento on MySQL and PHP, ASP.Net Storefront, or your custom SC are open
jsp shopping cart for transactions export into the text file or ready for their database table exposure via ODBC. We recommend quasi real time ecommerce integration approach, where you schedule IM integration via Windows macro shareware or freeware routines (or more advanced tool is available for purchase directly from Microsoft Business Solutions). But, IM is end user friendly tool, especially when you are planning to base it on text files there are examples on each scenario in Integration Manager default database (installed automatically). You keep your existing site and export newly checked out shopping carts either into the text files with folder controlling mechanism (exported, processed, exceptions with notification to the IT team), or even open ecommerce SQL database (you are not restricted to Microsoft SQL Server, it might be on Oracle, MySQL with PHP, FoxPro, MS Access, Pervasive SQL, anything that is ODBC compliant). We serve you USA/Canada nationwide via remote support (web sessions and phone/Skype conferences).
