Search Results Count is not working in AI search and Navigation tabs are blocked
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-05-2023 06:57 PM
Hello all,
When I am trying to search any catalog item or knowledge article search result is getting displayed but AI search navigation tabs are blocked and the show search results count is showing as (0) on the portal. Observed the count is coming from 'Show Search Results Count' in 'Search Application Configuration'.
I have checked the show search results count checkbox in the backend search application configuration but its still not working .
I have attached the images
Regards,
Sree
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2023 04:49 PM
Hi there,
We've been having the same issue. Our workaround was to go to the Search Application Configuration and turn the 'Show Search Results Count' off. The navigation tabs then began working as before.
By the way, if you then go back and mark the count as active again, you'll get a warning saying 'Please note, search results displayed and the total search count may vary due to security permissions. Search count can be disabled by deselecting the Show Search Results Count check box.' - I assume this is the cause of the problem. Hopefully SN will fix it soon, as I really like the look of the count.
Hope this helps. 🙂

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2024 04:42 AM
Hi All,
we are experiencing the same after the upgrade to Vancouver and disabling the counts seems to be the only option.
Did anyone already raise this issue to the ServiceNow support? Do you know if there already is a PRB ticker we could follow?
Thank you

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-27-2024 12:53 PM
hi, also experiencing this on an instance i am working on, do you have a solution or a workaround for this now?