|
Microsoft Great Plains integrations scenarios with legacy techniques, EDI, software customizations plus modifications upgrade We would want to describe many common scenarios from technical standpoint, their performance plus feasibility, including following help plus upgrade o Microsoft Dexterity integration. You can have these custom integrations, created in Great Plains Dexterity to learn tab delimited text data or ODBC information. Today, Microsoft Dynamics GP Integration Manager should do nearly all of the work. o Integration Manager. This tool is user-friendly plus intuitive. Historically IM had downside - it was utilizing Microsoft Great Plains OLE host, validating business logic via hidden types - the downside was moderate performance. However IM is a blog on how of being rewritten with eConnect, upcoming topic. o eConnect - initially it was meant because a tool for eCommerce programmer to use GP because accounting back host. eConnect breaks throughthe limitations plus complexity of pure Dexterity development plus through its many interfaces (including XML Internet Services) opens up GP objects to .Net programmer. eConnect is realized for core plus many popular modules, though in some instances you may discover that it is actually not realized for the component you meant for your integration (Invoicing, for example). eConnect is very efficient plus has excellent performance o SQL Stored Procedures. This scripting is especially effective at the same time needs superior learning of information distribution (plus some learning of Microsoft Dexterity architecture). The 1st guidance might be - create meant deal through GP interface plus carefully analyze where information goes plus then imitate your integration scripts. SQL Stored Procs provde the ideal performance, therefore your integration processes significant amount of transactions - you may end as much as use SQL scripts Alba Spectrum Group 1-866-528-0577, 1-630-861-5918, help@albaspectrum.com
edi software
Related Articles -
edi, software,
| 
