eQuipAPI

GetNamedSearchConfigFieldWithoutAdvanceFilter

The following routes are available for this service:
All Verbs	/GetNamedSearchConfigFieldWithoutAdvanceFilter/{UserID}/{ConfigID}

**GetNamedSearchConfigFieldWithoutAdvanceFilter** Parameters:
Name	Parameter	Data Type	Required	Description
UserID	path	string	No
ConfigID	path	string	No

**GetNamedSearchConfigResponse** Parameters:
Name	Parameter	Data Type	Required
SearchFieldCollection	body	List<SearchField>	No
AssetCategory	body	List<Dictionary>	No
IsLocked	body	bool	No
AtchtSearchReturnExactMatch	body	bool	No

**SearchField** Parameters:
Name	Parameter	Data Type	Required
ID	body	int	No
Name	body	string	No
Display	body	string	No
Type	body	short	No
DefaultValue	body	string	No
DefaultValueText	body	string	No
FieldDataSource	body	List<Dictionary>	No
UseMultiSelect	body	bool	No
FormName	body	string	No
IsSearchAsTextbox	body	bool	No
valuelistType	body	short	No
Operator	body	string	No
PrecisionFormat	body	int	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/GetNamedSearchConfigFieldWithoutAdvanceFilter HTTP/1.1 
Host: equipstage2.e-isg.com 
Content-Type: application/json
Content-Length: length

{"UserID":"String","ConfigID":"String"}

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

{"SearchFieldCollection":[{"ID":0,"Name":"String","Display":"String","Type":0,"DefaultValue":"String","DefaultValueText":"String","FieldDataSource":[{"String":{}}],"UseMultiSelect":false,"FormName":"String","IsSearchAsTextbox":false,"valuelistType":0,"Operator":"String","PrecisionFormat":0}],"AssetCategory":[{"String":{}}],"IsLocked":false,"AtchtSearchReturnExactMatch":false}