When a user enter a search for a particular record, can the result return display multiple field. We have a few duplicate valveID. Instead of returning v-155 three time can I config. the search result to display valveID and system field?
In C:\arcgis-web-appbuilder-2.1\server\apps\9\configs\Search\config_Search.json, I tried to change the displatField but the search did not work. Is this possible?
Ha,
You would have to add a suggestionTemplate property:
suggestionTemplate: "ID: ${ValveID}, System: ${System}",
Thanks, Robert. I tried your suggestion but it return the same three result. Am I missing something?
{
"layerId": "AquaGIS_Search2_6622_1",
"url": "MyServiceURL",
"name": "Valves Search",
"placeholder": "Place or Address",
"searchFields": [
"ValveID"
],
"displayField": "ValveID",
"suggestionTemplate": "ID: ${ValveID}, System: ${System}",
"exactMatch": true,
"searchInCurrentMapExtent": false,
"zoomScale": 2400,
"maxSuggestions": 6,
"maxResults": 6,
"type": "query",
No. You will only get the double field when a suggestion is presented by the widget.
Robert,
Can you clarify this a bit. I'm currently using ArcGIS Server 10.4.1 which should Supports Pagination: true. I did get a suggest of a single field but not double field. Do I needs to add the system field to the property "displayField"?
Ha,
No if you read the documentation on the search widget you will see that the displayField can only contain one field name and the suggestionTemplate:
(Added at v. 3.14) A template string used to display multiple fields in a defined order. This only works with feature layer sources and takes precedence over
displayField.
Thanks, Robert. It make sense know. I just have to switch my MapServer to FeatureServer and the suggestion should be presented by the widget. Right?
Nope. The use of a MapServer url is fine as long as you are adding a FeatureLayer as the search widgets source. The only reason to use a FeatureServer ul is when you want to edit that layer.
Robert, you got me going in circle. It turns out that I'm already using a dynamic feature layer as a source for searching, which I published as a MapServer. Your suggestion of using a suggestionTemplate did not working for me.
Can you help me determine what I did wrong or point me to a direction of how to display multiple fields.
Thanks,
Ha
Ha,
What Robert by featurelayer via your mapserver is this: http://services.arcgis.com/b6gLrKHqgkQb393u/arcgis/rest/services/TaxParcelQuery/MapServer/0
Baba
My mapserver source for searching look like this.
http://pabry280/arcgis/rest/services/AquaGISServices/AquaGIS_Search2/MapServer/1
Ha,
So after checking the search widgets code in WAB the suggestionTemplate is not used in the code. It get it working you will have to add these lines of code to the search/Widget.js file (lines 16 - 19):
var convertedSource = {
featureLayer: flayer,
outFields: ["*"],
searchFields: fNames,
displayField: source.displayField || "",
exactMatch: !!source.exactMatch,
name: jimuUtils.stripHTML(source.name || ""),
placeholder: jimuUtils.stripHTML(source.placeholder || ""),
maxSuggestions: source.maxSuggestions || 6,
maxResults: source.maxResults || 6,
zoomScale: source.zoomScale || 50000,
infoTemplate: template,
useMapExtent: !!source.searchInCurrentMapExtent,
_featureLayerId: source.layerId,
};
if(source.suggestionTemplate){
delete convertedSource.displayField;
convertedSource.suggestionTemplate = source.suggestionTemplate;
}You are the man. See Robert, I new that there was something missing and not just adding a suggestionTemplate property. It works great. Thanks you for your time and bearing with me in trying to explain my issue.
To those who wanted to do this.
Recap of what I did base on Robert suggestion.
Add code to widget.js and config_Search.json. See below.....
Thanks,
Ha Thach
Robert - I got the suggestionTemplatet to work but despite setting it to exact match, the search executes a LIKE search. Is there a way to fix this?
Ha Thach,
Having suggestion enabled if you want to use exact match is counter productive. The whole purpose of suggestions is to provide possible result using a like if you do not want this then disable suggestions. What the exact match does is it will force you to choose one of the suggestions to get a result if you did not have exact match selected and you type 862 and hit enter then the first result that matched 862 would be selected.
Thanks, Robert for your input. The simple solution on my end would be to increase the "maxSuggestions" result value.
Ha,
So after checking the search widgets code in WAB the suggestionTemplate is not used in the code. It get it working you will have to add these lines of code to the search/Widget.js file (lines 16 - 19):