| All Verbs | /AddToListUsingTransaction |
|---|
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| TransactionTableID | query | int | No | |
| UserID | query | string | No | |
| AssetList | query | string | No | |
| TransactionID | query | int | No | |
| HideGrouplist | query | bool | No | |
| AssetSearchConfigID | query | string | No | |
| WorkFlowID | query | string | No | |
| MainAssetId | query | int | No | |
| isHeaderAsset | query | string | No | |
| IsFromAssemblyTransactionWorkflow | query | bool | No | |
| ReservationID | query | string | No | |
| IsfromCheckin | query | bool | No |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /xml/oneway/AddToListUsingTransaction HTTP/1.1
Host: equipstage2.e-isg.com
Content-Type: application/xml
Content-Length: length
<AddToListUsingTransaction xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<AssetList>String</AssetList>
<AssetSearchConfigID>String</AssetSearchConfigID>
<HideGrouplist>false</HideGrouplist>
<IsFromAssemblyTransactionWorkflow>false</IsFromAssemblyTransactionWorkflow>
<IsfromCheckin>false</IsfromCheckin>
<MainAssetId>0</MainAssetId>
<ReservationID>String</ReservationID>
<TransactionID>0</TransactionID>
<TransactionTableID>0</TransactionTableID>
<UserID>String</UserID>
<WorkFlowID>String</WorkFlowID>
<isHeaderAsset>String</isHeaderAsset>
</AddToListUsingTransaction>