eQuipAPI

GetAssetUserFieldData_V2

The following routes are available for this service:
All Verbs	/GetAssetUserFieldData_V2/{UserID}
All Verbs	/GetAssetUserFieldData_V2/{UserID}/{LastSyncDate}
All Verbs	/GetAssetUserFieldData_V2/{UserID}/{LastSyncDate}/{RecordSize}
All Verbs	/GetAssetUserFieldData_V2/{UserID}/{LastSyncDate}/{RecordSize}/{LastAssetIDInternal}

**GetAssetUserFieldData_V2** Parameters:
Name	Parameter	Data Type	Required
UserID	path	string	No
LastSyncDate	path	string	No
LastAssetIDInternal	path	string	No
RecordSize	path	int?	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/reply/GetAssetUserFieldData_V2 HTTP/1.1 
Host: equipstage3.e-isg.com 
Content-Type: application/xml
Content-Length: length

<GetAssetUserFieldData_V2 xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <LastAssetIDInternal>String</LastAssetIDInternal>
  <LastSyncDate>String</LastSyncDate>
  <RecordSize>0</RecordSize>
  <UserID>String</UserID>
</GetAssetUserFieldData_V2>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<ScannerFieldData xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <Asset_ID_Internal>String</Asset_ID_Internal>
  <ScannerField>String</ScannerField>
</ScannerFieldData>