<back to all web services
CheckRequestedQuantityForTemplateRecord
The following routes are available for this service:| All Verbs | /CheckRequestedQuantityForTemplateRecord | | |
|---|
CheckRequestedQuantityForTemplateRecord Parameters:| Name | Parameter | Data Type | Required | Description |
|---|
| UserID | query | string | No | |
| TemplateRecordID | query | int | No | |
| WorkflowID | query | string | No | |
| TransactionDetailTableCollection | query | List<SearchParamForTransactionDetailTable> | No | |
SearchParamForTransactionDetailTable Parameters:| Name | Parameter | Data Type | Required | Description |
|---|
| FieldID | body | string | No | |
| FieldName | body | string | No | |
| FieldValue | body | Object | No | |
| Operator | body | string | No | |
| FieldType | body | short | No | |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /xml/oneway/CheckRequestedQuantityForTemplateRecord HTTP/1.1
Host: equipstage3.e-isg.com
Content-Type: application/xml
Content-Length: length
<CheckRequestedQuantityForTemplateRecord xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
<TemplateRecordID>0</TemplateRecordID>
<TransactionDetailTableCollection>
<SearchParamForTransactionDetailTable>
<FieldID>String</FieldID>
<FieldName>String</FieldName>
<FieldType>0</FieldType>
<FieldValue />
<Operator>String</Operator>
</SearchParamForTransactionDetailTable>
</TransactionDetailTableCollection>
<UserID>String</UserID>
<WorkflowID>String</WorkflowID>
</CheckRequestedQuantityForTemplateRecord>