Select to view content in your preferred language

Search Widget - Enterprise 11.3

176
3
Jump to solution
11-05-2024 09:02 AM
mhudson
Occasional Contributor

We recently updated to Enterprise 11.3 and started noticing some odd behavior with the Search Widget. After doing research and looking at the Search Widget help page, it appears it's a new "feature" with Enterprise 11.3 that changes how the Search Widget functions.

https://doc.arcgis.com/en/experience-builder/11.3/configure-widgets/search-widget.htm

It no longer does at CONTAIN %abc% search but a full-text search. Why did ESRI change this? It is not a helpful change to how the widget works. It's actually a step backwards in functionality.

Is there a way to get around this new limitation at Enterprise 11.3?

0 Kudos
1 Solution

Accepted Solutions
DanCopKac
Frequent Contributor

Lol wait till you find out you can no longer open PDFs directly in the browser. 

Note that the actual search results still use CONTAIN %abc%. If you disable search suggestions (set it to 0) then it forces the user to always press enter after typing in their search term. This produces the CONTAIN results. 

Not really an improvement, no matter how you cut it, but an illusion that can make the new deficiency less apparent to users. 

View solution in original post

3 Replies
DanCopKac
Frequent Contributor

Lol wait till you find out you can no longer open PDFs directly in the browser. 

Note that the actual search results still use CONTAIN %abc%. If you disable search suggestions (set it to 0) then it forces the user to always press enter after typing in their search term. This produces the CONTAIN results. 

Not really an improvement, no matter how you cut it, but an illusion that can make the new deficiency less apparent to users. 

mhudson
Occasional Contributor

DanCopKac,

That did the trick for our experience. I appreciate the help on this. 

Thank you!

0 Kudos
DavidRasner1
Occasional Contributor

The search widget used to work perfectly fine, the newest update broke it. Reducing the result suggestions to 0 is one workaround, another idea is to create a custom search widget using AI. I made one using Claude, it's just 100 lines of code and works fine.

0 Kudos