Differences between the XML Message Pusher and the XML Direct Document Sender applications with eConnect Content provided by Microsoft Applies to: eConnect Select Product Version All Products TechKnowledge Content SUMMARY The install of eConnect comes with various sample applications. There are two very useful samples:XML Message Pusher at C:\Program Files\Microsoft Great Plains\eConnect75\eConnect Samples\Queue ClientXML Direct Document Sender at C:\Program Files\Microsoft Great Plains\eConnect75\eConnect Samples\XMLDirectDocumentSenderMORE INFORMATION Though the applications appear to be similar, they work very differently. The XML Message Pusher will take an XML document and place it on a queue. It does not pass the XML document to Great Plains directly. Once it is on the queue, the Incoming Service or BizTalk need to pick the message up off the queue and pass it to Great Plains. This would be the utility to use when testing the Incoming Service or BizTalk. If testing is being done with the .Net API, this utility can be used with the Incoming Service and Microsoft Message Queuing. The Incoming Service uses the .Net API.The XML Direct Document Sender will pass the XML document to the eConnect COM Object which then passes it on to Great Plains. The XML Direct Document sender does not put messages on to the queue. This would be the application to use to test document when passing them to the eConnect COM Object.Source code for each of the samples can be found in their respective directories. These are Visual Basic 6.0 applications.This article was TechKnowledge Document ID: 34468 APPLIES TO • Microsoft Dynamics GP 9.0 • Microsoft Business Solutions–Great Plains 8.0 • Microsoft Business Solutions–Great Plains 7.5 • Microsoft Great Plains Dynamics 7.0 • Microsoft Great Plains eEnterprise 7.0 • eConnect Last Updated: 7 Mar 2017 Did this solve your problem? Yes No Tell us what we can do to improve the article Submit Thanks! Your feedback will help us improve the support experience.