Great Plains – If you are implementing Microsoft Dynamics GP in your organization, we would like to give you some specific implementation tips. You should read this article if you would like to stay on the Microsoft Dynamics GP implementation path.

Great Plains

In this article we will try to answer following questions:

1. Microsoft Dexterity vs. eConnect.
2. eCommerce integration with GP as well as eOrder, coming from eConnect.
3. Integration with Microsoft RMS.
4. GP user workstation detection in detail.
5. comprehensive overview of currently available GP custom integration tools.
6. Great Plains Dexterity. This technology is sometimes considered as the end-of-the-line technology and generally it is ready for a professional consultant to designed for you. However GP is very flexible and easy to be tailored and changed, as GP foundation is Microsoft Dexterity. Dexterity development could be outsourced, for example – Microsoft Great Plains Business Portal. Dexterity customization and web development could be given over to MBS partner. Typical custom logic is placing Customer info, Sales Order, GL account, etc. into work tables: Dynamics.dic, Reports.dic, or Dexterity forms. InAdjustment-o-MBS, we saw that GPIntegration module doesn’t deploy Dexterity in production mode. This is strange – considering that Dexterity is the integrating element: Integration.dic, VBA scripting, ReportWriter modifications, sites registry changes, encrypted JMS messages and so on. Maybe such surprises are related to the fact that fat client (mention), which is running behind the scenes, is not ASP.NET-based – but rather Microsoft SQL Server based ( Dynamics.dic )
7. eCommerce integration with Great Plains. Here we need to mention interesting fact, that eConnect direct eConnect session is slower than Microsoft Dynamics GP Datawarehousing. Plus you should allocate additional hardware resources for eConnect: Memory and Disk – it is not inexpensive option, moreover you should get eConnect Runtime, deploy it through command line – this obviously requires MS SQL Server. However if you are facing issues with eConnect – please reference your Microsoft Dynamics GP or Dynamics NAV developer, familiar with eConnect settings
8. R unsupported add-ons. Add-ons are frequently upgraded and released by Microsoft Business Solutions. At the same time – add-ons are also revised, especially in the case of Microsoft Great Plains – and as a rule they do not work with old versions of Great Plains (5.0, 5.5)
9. Switching from one ERP to another. You should know the history of Microsoft Great Plains – it was originally designed as Database (Accounts) module, later on it was transformed into its present form – Microsoft Dynamics GP. When Microsoft Business Solutions decided to develop Microsoft Dynamics GP – the cheapest and most flexible DB platform was chosen – it is MS SQL Server
10. GettingTROBASOken. If you are using Lotus Notes Domino – you may be able to utilize Domino lookup to Great Plains database for purposes of transferring your invoices. However returns data are stored in different Tables – than in Lotus and moreover you have to build transactions jump tables. This is why weNKOBJCTO conforms to Lotus Notes architecture and it is not applicable to Microsoft Great Plains – transactions should be stored in the native database
11. Additional Considerations. Besides of course the aboveIndustries: Please invest into derivatives of Great Plains: capture, export, quote, journal, etc. You can always appeal to our expertise. Give us a call: 1-630-961-5918, 1-866-528-0577,help@albaspectrum.com

Great Plains