Experience Builder Search Widget Slow

Question

I have been experiencing issues with the Search Widget in experience Builder. (I think we are on the latest portal version or the one before)

We have about 21 layers with a total of probably 240 000 features across them. I have set up the search widget to search three fields in all the layers. (We use our GIS system to create Equipment Master Data to SAP) The 3 fields are: Functional Location Field (That is unique when populated) 30 Char, Equipment Description 40 Char and MC Notification Number which is a 9 digit Number.

The suggested list of items popup fairly quickly, but selection after that takes probably anything from 5 to 15 seconds for the widget to react. (In Webapp Builder it did not take this long.) What is worst is the widget shows no Results. This is extremely frustrating. We cannot use query as that will search one layer at a time. We cannot use group filter as that will possibly hide duplicate equipment that we need to identify.

Alternative Map Search is faster, but I have found that some fields are missing from the selection on the Map. Also not sure why? So cannot add the MC Number field layer search in the Map. (Reference to Map settings, Application Search, By Layer)

Any ideas or assistance will be appreciated. I know this issue was partially covered in some of the posts, but have not seen a solution of clear work around to my issue as described above.

ShengdiZhang · Answer

Hi @becyr ,

We may still need a sample app to reproduce this issue. If you’re unable to share your app, please contact the Support team so they can assist in reproducing the problem.

Thanks,

Shengdi

becyr · Answer

Hi @ShengdiZhang,

I am also experiencing a slowdown in the search widget. The layer I am using is from ArcGIS Server; it has about 40,000 records. Do you want me to share a sample video?

TimWestern · Answer

I've seen similar slowness or no results in search widget also.  I think this is related to how react works and because you don't really know when searching has completed when you click on the suggestions (which is not the same as results), you may select a suggestion which does a new query and starts the search all over again in effect. All of these operations are asynchronous so I've thought perhaps remnants from the earlier search before selecting a suggestion take time to 'cancel' out.

I have also noticed that the speed of search is directly related to the number of columns/attributes having to be checked.  Naturally the more there are the slower it will return. At least that's been my experience.