- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2024 09:29 AM
Hello everyone,
I've encountered an issue that's giving me some trouble. I've configured the global search functionality to operate on custom tables, and it's functioning perfectly in the default view of the instance. However, when "glide.ui.polaris.experience" is set to true to enable the next experience view in the Vancouver version, the global search functionality doesn't behave as expected—it fails to display results. Interestingly, when I revert "glide.ui.polaris.experience" to false, returning to the old default view, the global search works flawlessly.
I'm wondering if there are any specific considerations I should keep in mind to ensure the global search functionality works seamlessly in the next experience view as it is the main requirement, or is it something that needs attention from the ServiceNow end?
Your assistance with this matter would be immensely appreciated.
Thank you!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-29-2024 02:20 PM
The Next Experience has different global search configurations comparing to core UI, make sure you follow the following documentation to add the table that you are looking for. so that, it is visible when you search for it.
Search settings filter and group global search results by table (servicenow.com) If you add the table to "sys_search_source.list' and then add the search source to "m2m_search_context_config_search_source.list" and make sure your table is text indexed.
After performing the steps in the documentation, you should be able to see the records from the table you added.
Hope it helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2025 11:59 AM
When "glide.ui.polaris.experience" is set to true to enable the next experience view in the UTAH version, the global search functionality, doesn't even show on the top bar let alone behave as expected—. Interestingly, when I revert "glide.ui.polaris.experience" to false, returning to the old default view, the global search shows
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Could this be because the web portal part was not upgraded correctly?
I'll have to watch out for any errors next upgrade
