topic Re: WAB Search Widget - Does Not Honor Web Map Filters or HTML tags in ArcGIS Web AppBuilder Questions

WAB Search Widget - Does Not Honor Web Map Filters or HTML tags

HeatherBerg — Wed, 17 Feb 2016 20:36:44 GMT

I have run into two issues using the Search Widget in Web AppBuilder. Any help remedying these issues is greatly appreciated.

1. Honoring Filters

I have set up a filter in the Web Map being references for the WAB app, but this filter is not being honored in the final Web AppBuilder application. When I enter in search criteria, a list of all of the features containing the search word are listed instead of limiting the list to only show the filtered features. Are filters supposed to carry over into WAB?

2. Recognizing certain HTML tags using the Search bar

I have also noticed that when a feature is selected using the search bar (left image), html tags in the photo credit and image are not displaying correctly. If I click on the same feature in the map itself (right image), everything works perfectly. Is there a reason for this?

URL for WAB: http://sdgfp.maps.arcgis.com/home/item.html?id=87004e16337d4462bb3b6a53fdf6ed8e

URL for Web Map: http://sdgfp.maps.arcgis.com/home/item.html?id=b05c0e0b28c745dab08ecd1908720fca

Thank you!!

Re: WAB Search Widget - Does Not Honor Web Map Filters or HTML tags

YueWu1 — Thu, 18 Feb 2016 00:00:33 GMT

Hi Heather,

For the first question, we have already has a bug created related to this issue:

[BUG-000090789 The Web AppBuilder Query widget does not reflect the filtered values from the ArcGIS Online map viewer.] This bug is already put in product plan.

Re: WAB Search Widget - Does Not Honor Web Map Filters or HTML tags

RobertScheitlin__GISP — Thu, 18 Feb 2016 13:45:21 GMT

Heather,

For the second part of your question, as neither of the urls you provided above are publicly accessible it is difficult to test. But if they were publicly accessible one of the first tests I would run would be to take the web map id and add it to the web map by id JS API sample and see if it exhibits the same issue. That way I could narrow down the issue to WAB or just a JS API issue.