eQuipAPI

FindLegacyWorkOrders

Returns a list of LegacyWorkOrders; Requires a valid user to complete this request.

The following routes are available for this service:
POST	/maintenancemanagement/legacyworkorders	Returns list of legacy work orders	We used POST in lieu of GET as the request can exceed the allowable GET size threshold.

**FindLegacyWorkOrders** Parameters:
Name	Parameter	Data Type	Required	Description
UserID	query	Guid	Yes	The UserID that authorizes the caller to complete the request. Contact your eQuip admin.
SearchCriteriaCollection	body	List<SearchParam>	No	Search criteria collection of legacy work orders
take	body	int	No	The number of work orders to return. 0 returns all entries;Used only by Telerik UI components
skip	body	int	No	The page offset to start retrieving data. 0 returns first page entries;Used only by Telerik UI components
sort	body	IEnumerable<Sort>	No	The collection of field and direction to sort legacy work orders;Used only by Telerik UI components
filter	body	Filter	No	The parameters collection to filter legacy work orders;Used only by Telerik UI components

**SearchParam** Parameters:
Name	Parameter	Data Type	Required
FieldID	body	string	No
FieldName	body	string	No
FieldValue	body	Object	No
Operator	body	string	No
FieldType	body	short	No
UseMultiSelect	body	bool	No
IsSearchAsTextbox	body	bool	No
IsTransactionDetailSearch	body	bool	No
IsSubTransactionDetailSearch	body	bool	No
SecondDateRangeValue	body	string	No

**Sort** Parameters:
Name	Parameter	Data Type	Required	Description
Field	body	string	No
Dir	body	string	No

**Filter** Parameters:
Name	Parameter	Data Type	Required
Field	body	string	No
Operator	body	string	No
Value	body	Object	No
Logic	body	string	No
Filters	body	IEnumerable<Filter>	No

**DataSourceResultResponse** Parameters:
Name	Parameter	Data Type	Required
Data	body	IEnumerable	No
Total	body	int	No
IncludeLinkTotal	body	int	No
Aggregates	body	Object	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /json/reply/FindLegacyWorkOrders HTTP/1.1 
Host: equipstage3.e-isg.com 
Content-Type: application/json
Content-Length: length

{"UserID":"String","SearchCriteriaCollection":[{"FieldID":"String","FieldName":"String","FieldValue":{},"Operator":"String","FieldType":0,"UseMultiSelect":false,"IsSearchAsTextbox":false,"IsTransactionDetailSearch":false,"IsSubTransactionDetailSearch":false,"SecondDateRangeValue":"String"}],"take":0,"skip":0,"filter":{"field":"String","operator":"String","value":{},"logic":"String"}}

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

{"Total":0,"IncludeLinkTotal":0,"Aggregates":{}}