These off-base matches happen because of how the platform ranks and filters navigation results. By default, a system property called glide.ui.polaris.nav_filter_accuracy_score is set to 75, which allows for fuzzy matching. That means it tries to be "helpful" by returning loosely related terms.
Helpful? Not really—especially when you're just trying to get to the right module quickly.
The Fix: Dial the Accuracy to 100
Set the property value to 100, and the navigator will only return precise results. No more guessing what ServiceNow thinks you meant. Here's how to do it:
-
In the Application Navigator, manually type:
sys_properties.list -
Search for:
glide.ui.polaris.nav_filter_accuracy_score -
Set its value to 100 and save
Pro tip: Don’t rely on the navigator search to find this property—you’re fixing the very problem that would cause it to fail 😉
Why 100 Makes Sense
Unless you're using the navigator like a knowledge search (you shouldn't be), fuzzy results are more noise than signal. As your instance grows with custom apps, plugins, and modules, precision matters more than ever.
Does this new "feature" doesn't help at all? Leave a comment, let's chat.
Leave a thumbs up either way
2 Comments
