🔍 Global search is missing from instance?

tiagomacul · 3 hours ago

The global search bar is essential for the day-to-day agility of ServiceNow. When it simply doesn't appear , it can disrupt the workflow of the entire team.

This guide details how to diagnose and correct this problem using the Global Text Search settings and supplementing KB2112361 .

If I haven't been clear enough about the context of the behavior:

What is unexpected?

Notice that in the image above we don't have the global marker, but in the image below the global marker appears.

Step 1: Checking System Properties

Often, the feature is simply disabled in the global settings. To check, follow the path below as illustrated in the image:

Navigation Route:

In the main menu, click on the All tab .
In the filter field (Filter Navigator), type: global text search.
Find and click: System Properties > Global Text Search .

Key Property:

Within this screen, look for the property:

Name: glide.ui.text_search.enable
Value: Make sure it is set to true .

https://<instance>.service-now.com/now/nav/ui/classic/params/target/sys_properties_list.do%3Fsysparm_query%3Dname%253Dglide.ui.text_search.enable%26sysparm_first_row%3D1%26sysparm_view%3D

Note: If global search does not appear even with this property enabled, the system may be experiencing a cache or permission conflict.

Step 2: Other Common Causes

If the above information is correct and the magnifying glass icon still doesn't appear, check these points:

1. AI Search Configuration (Next Experience)

In recent instances, the standard search has been replaced by AI Search .

Verification: If AI Search is enabled but the search profile is not configured for your application's header, the search bar will be invisible.

2. Roles and Permissions

The global search can be restricted to specific roles.

Test: Check if the search appears for the Admin user . If it only appears for them, review the table permissions sys_search_scope.

3. Plugins Disabled

Functionality depends on the Zing or AI Search search engine . Check if the base plugins (such as the one provided com.glide.sn_zig) are active.

Step 3: Validation in Next Experience (UX Page Properties)

If your instance uses the new interface (Polaris), global search depends on a specific page property.

Navigate to the property globalSearchDataConfigIdvia this direct link:/nav_to.do?uri=sys_ux_page_property.do?sys_id=33922957c7b32010099a308dc7c26072
```
https://<instance>.service-now.com/now/nav/ui/classic/params/target/sys_ux_page_property.do%3Fsys_id%3D33922957c7b32010099a308dc7c26072
```
In the Value field , ensure there is a valid Sys ID pointing to your page's search configuration. If this field is empty or contains an incorrect ID, the search bar will not render.

KB2112361 mentions reverting to a previous version, something that might not be available; I had the ID .

c861cea2c7022010099a308dc7c26041
6ebf8fe1531201107f03ddeeff7b122b

These IDs refer to the sys_search_context_config table.

[AIS] Next Experience Search Configuration

6ebf8fe1531201107f03ddeeff7b122b

Now Experience Search Configuration

c861cea2c7022010099a308dc7c26041

Quick Verification Summary

Where to Check	Action Needed
System Properties	`All > Global Text Search > glide.ui.text_search.enable = true`
AI Search	Confirm that the service is "Active" and has generated indexes.
User Profiles	Ensure that the user has the necessary role to view the search scope.

Official Technical Reference

For details on known bugs in specific versions, please consult the official documentation:

Access KB2112361 (ServiceNow Support)

Participate, join the communities, follow the posts: