Dynamics F/SCM Customer Experience (CRM) Dynamics GP Dynamics Business Central (NAV) Dynamics SL Power Platform Fabric Copilot

[Karen Porter]

I have been digging into trying to learn eConnect and creating my own .NET application to use for integrating sales invoice transactions to GP2015. I have been using the sample console application as a starting point. It’s a great start and I have been successful in pushing a single sales invoice transaction. However, I am wondering if I could get any guidance in how the XML structure would look for more than 1 transaction. I have searched and searched and not found one for multiple transactions. Ideally I will use a SQL select statement to pull the data and then I would like to loop through that data and build the XML document.

I know the very basic structure for one invoice transaction with multiple line items would be as shown below. For me to send multiple transactions in a single XML document, would it just be the idea of adding another <SOPTransactionType> node (as shown in bold below) with the line item and header info?

<eConnect>

    <SOPTransactionType>
        <taSopLineIvcInsert_Items>
            <taSopLineIvcInsert>
                  … line item 1
            </taSopLineIvcInsert>
            <taSopLineIvcInsert>
                  … line item 2
            </taSopLineIvcInsert>
        </taSopLineIvcInsert_Items>
        <taSopHdrIvcInsert>
                  … invoice header
        </taSopHdrIvcInsert>
    </SOPTransactionType>
    <SOPTransactionType>  –would I add another node here for another transaction??
    </SOPTransactionType>
</eConnect>

——————————
Karen Porter
American Innovations
Austin TX
——————————

[Blair Christensen]

Looks right to me.  Are you using a test box to do your development against?

——————————
Blair Christensen
Database Administrator
Oppenheimer Companies, Inc.
Boise Idaho GPUG Chapter Leader
——————————
——————————————-

[Lucas Miller]

Hello Karen,

Each call to the <eConnect> node should only contain the information for a single transaction.  This has to do with the use of SQL transactions for the associated call to the Dynamics GP database(s).  If there is some logic error returned by eConnect it will roll-back the transaction, but if you have multiple transactions in the same XML then it could potentially roll back the ones that were successfully integrated.

I’ve also heard of some performance implications around having long-running SQL sessions which can be mitigated by limiting to one transaction per XML that is submitted to the eConnect Integration service.

Let us know if you have further questions on this!

——————————
Lucas Miller
Support Escalation Engineer
Microsoft
Fargo, ND
——————————
——————————————-