This article is dedicated to Microsoft Great Plains eCommerce and web software development primarily, plus Microsoft Dynamics GP customization, integration, data conversion and reporting. As software programmer you should know where one customization realm exists and where it has boundaries: new and legacy technologies, such as Microsoft Great Plains Dexterity, eConnect, VBA & GP Integration Manager

eConnect was initially introduced for e-commerce web developers, enabling them to link ecommerce web site with Microsoft Dynamics GP on the back end as accounting or ERP

Dexterity. This technology was introduced in late 1980th and earlier 1990th as EDI and programming language (sanscript) for new Great Plains Software MRP platform Great Plains Dynamics, coming up to replace former ERP Great Plains Accounting (available for DOS and MS Windows in 1990th and earlier). Dexterity was archtectured to provide computer graphical platform independence (remember software platform battles: Microsoft Windows, MAC OS, Solaris, etc.) and SQL and DB platform relative independence and portability. Dexterity was securing Great Plains Dynamics future, regardless on who wins on both: computer operating system and database directions

Programmers pools. Dexterity programmers are not often found on the job and consulting market nowadays, however they were available in late 1990th and earlier 2000th. eConnect in turn uses modern Microsoft technologies, such as .Net, c#, VB, SQL scripting, MS Visual Studio, as well as universal new software development tools, such as XML web services, eConnect gives you as a developer access to the set of Dynamics GP objects: Customer, Vendor, Sales Order, etc. So, it would be probably fair to say, that eConnect programmers are available on the market, and even if universal .Net developer is not familiar with eConnect yet he will read documentation and will be able to program in a very short turning time

eConnect flexibility. Being reflection (so far) of what was initially created on GPS Dexterity platform, econnect, has restrictions on the subset of objects its scope is broad, but limited in comparison to original Dexterity. Another eConnect limitation is posting (and SOP order transfer to invoices and backorders)

Dexterity flexibility. Being legacy platform, dex should be considered with certain level of respect, however with the software development tool life cycle precaution

Recommendations. If you need to cross eConnect limitation boundaries, you should rescue to Dexterity development. Dexterity developers should have access to Dexterity source code (DYNAMICS.DIC with sanscript code) in this scenario your customization possibilities are unlimited.

Please feel free to call us: 1-866-528-0577, 1-630-961-5918, help@albaspectrum.com skype: albaspectrum

About the author:
Andrew Karasev, Alba Spectrum Group (http://www.albaspectrum.com  http://www.enterlogix.com.br ), serving clients in IL, TX, CA, IN, WI, MI, NY, FL, CO, GA, LA, WA, NV, AZ, KA, plus we can help you internationally, where GP is supported: Canada, Australia, New Zealand, Oceania, Pakistan, Middle East, UK, Mexico, Argentina, Chile, Colombia, Venezuela. We are ready with large scale customization and industry solutions: Aerospace & Defense, Oil & Gas, Distribution & Logistics, Manufacturing & Assembling, Consignment & Warehouse Management (incl. Barcode Solutions), Beverages, Suply Chain Management, and others.

To read more articles on Textile, Fashion, Apparel, Technology, Retail and General please visit www.fibre2fashion.com/industry-article/