topic New Hub Search Experience Persisting Categories and Groups in ArcGIS Hub Questions

New Hub Search Experience Persisting Categories and Groups

KristenWobbe1 — Sat, 20 Jan 2024 00:49:41 GMT

The new Hub Search Experience rolled out on Jan. 9th, 2024, and we noticed some unexpected behavior. It is our experience that the issue is that CATAGORIES AND GROUPS PERSIST ACROSS THE WHOLE SESSION in the Explore URL, AND CATEGORIES HAVE 'RESET, but there is NO 'RESET' FOR GROUP (seems to be new in /explore). See workflow and screenshots from our testing below on a basic example:

Go To a search with a group Id parameter: https://gbp-blm-egis.hub.arcgis.com/search?groupIds=34b45b241be74f3e8f471df0700f1fb8

From there, go to the Home Page and Search for something...

The groupIds parameter persists...

The issue seems to be NOT clearing out the groupsIds parameter. The search parameters ARE persisting when moving from search pages with the new search experience.

Our question is whether this could possibly be just an oversight on the part of the ESRI ArcGIS Hub Team, and if there could potentially be a quick fix?

Re: New Hub Search Experience Persisting Categories and Groups

ThomasHervey1 — Sun, 21 Jan 2024 14:58:40 GMT

Hello @KristenWobbe1
Thanks for your post. We've identified the cause of the issue and we're working on a resolution as soon as possible. Please stay tuned to the Hub changelog. Once complete, when a user executes a new blank search from a different part of the application (such as the global navigation search bar), then previous filters including groupIds will be removed.

Given that many customers use group filters explicitly to show end users a smaller subset of results but the values are not clear to end users, we've intentionally obstained from adding a filter for groupIds. However, as you've noted the filter should be reset when executing a new search.

Re: New Hub Search Experience Persisting Categories and Groups

KristenWobbe1 — Mon, 22 Jan 2024 17:58:37 GMT

Many thanks! We will keep an eye 👀 on the Changelog for implementation of this resolution. 🙂