<eConnectProcessInfo>

Additional information

The <eConnectProcessInfo> XML node controls incoming and outgoing processing. Each eConnect schema requires you to include the <eConnectProcessInfo> XML node in the document.

Element name

Data type

Description

ConnectionString

string

Override the default connection string.

ProductName

string

Contains the correct product name for each ISV document that is integrated. The <ProductName> element should be filled in with the ISV product name that was used when the registration keys were generated. <ProductName> is for developer use only.

Sender

string

Enables third parties to differentiate one trading partner document from another trading partner document; that is, if the failed partner document fails, they know which sender to contact.

Outgoing

string

Specifies an outgoing message; Outgoing=TRUE.

EConnectProcsRunFirst

string

Specifies the order in which the core eConnect Procedures will run; eConnectProcsRunFirst=TRUE

MessageID

string

Acts as a descriptor for the message, which is used for tracking.

SiteID

string

Available for use.

DocumentName

string

Is available for future use.

Version

string

Identifies the version.

DateTimeStamp1

datetime

Is filled with value when XML processing begins.

DateTimeStamp2

datetime

Is filled with value when XML processing ends.

DateTimeStamp3

string

Is available for use.

DateTimeStamp4

string

Is available for use.

DateTimeStamp5

string

Is available for use.

Userdef1

string

Is available for use.

Userdef2

string

Is available for use.

Userdef3

string

Is available for use.

Userdef4

string

Is available for use.

Userdef5

string

Is available for use.

ProcReturnCode

string

Returns an error message value.

The <eConnectProcessInfo> node should always follow the transaction type node. The following XML document example uses the ConnectionString element of the <eConnectProcessInfo> node to make inventory changes in two different company databases. The first SMInventoryItemSiteType transaction type assigns item number 256 SDRAM to the location 0095 of the TWO company. The second SMInventoryItemSiteType assigns the item number 128 SDRAM to the 0095 location of the TEST company.

<eConnect xmlns:dt="urn:schemas-microsoft-com:datatypes">
    <SMInventoryItemSiteType>
        <eConnectProcessInfo>
            <ConnectionString>
                Integrated Security=SSPI;
                Persist Security Info=False;
                Initial Catalog=TWO;
                Data Source=machinename
            </ConnectionString>
        </eConnectProcessInfo>
        <taItemSite>
            <ITEMNMBR>256 SDRAM</ITEMNMBR>
            <LOCNCODE>0095<LOCNCODE>
        </taItemSite>
    </SMInventoryItemSiteType>
    <SMInventoryItemSiteType>
        <eConnectProcessInfo>
            <eConnectProcsRunFirst>TRUE</eConnectProcsRunFirst>
            <ConnectionString>
                Integrated Security=SSPI;
                Persist Security Info=False;
                Initial Catalog=TEST;
                Data Source=machinename
            </ConnectionString>
        </eConnectProcessInfo>
        <taItemSite>
            <ITEMNMBR>128 SDRAM</ITEMNMBR>
            <LOCNCODE>0095</LOCNCODE>
        </taItemSite>
    </SMInventoryItemSiteType>
</eConnect>