Skip to main content

Notifications

Microsoft Dynamics GP (Archived)

eConnect 2010 new method questions

Posted on by 100

Hi all:

We are trying to upgrade an existing integration porject from eConnect 10 to eConnect 2010 but have a couple of questions:

1. The eConnect 2010 seperates the eConnect_EntryPoint method to two methos - CreateEntity and CreateTransactionEntity. In eConnect 10 we can just simply send an xml document to one consistent entry point (which resides on a web method provided by a web service). But now how do I know which method I need to call from business layer? (which means we need to either pass the type as parameter or create two web methods for entity and transaction). 

2. Furthermore, if I have mixed the entities and transactions in one xml document, which method I should call?

 Does anyone have the same issue or have the solution?

Thanks,

*This post is locked for comments

  • Winson Huang Profile Picture
    Winson Huang 100 on at
    Re: Re: eConnect 2010 new method questions

    Hi Louis:

     Thanks for your reply.

     We will do that way.

  • Re: eConnect 2010 new method questions

    Hi Winson,
    We are very excited that you decided to upgrade to eConnect 2010!

    The reason for the new methods is to allow for future upgrades to the functionality of eConnect without having to change the interface.

    The CreateEntity method is intended for Dynamics GP Master Records that do not deal with any type of financial transactions. (e.g. Customer, Vendor, Employee, Item, etc…)
    The CreateTransactionEntity method is intended to be used when creating transactions. (e.g. Sales Order, POP, etc…)

    The reason for separate methods is to help consumers of eConnect split up their documents into functional pieces. This helps organize the data going into eConnect and it also allows for eConnect to wrap each document with a separate SQL transaction. This way it is easier to troubleshoot which documents failed and why they failed.

    We suggest consumers to send in separate xml’s (<eConnect></eConnect>) for each entity they want to create.

    If you need to create masters records (e.g. Customer) at the same time as creating a Transaction (e.g. Sales Order) then you can pass this XML document into the CreateTransactionEntity method. We recommend that you create a master record separately, and outside the scope of a Financial Transaction document.

    http://msdn.microsoft.com/en-us/library/ff623630.aspx

    Hopefully this helps you distinguish the difference between the methods.

    As you probably already noticed we have depreciated the original two methods in favor of the new interface.

    Please let us know if you have any additional questions.

    Regards,
    Louis

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Community AMA December 12th

Join us as we continue to demystify the Dynamics 365 Contact Center

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,240 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,149 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans