Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Exact search is not working with New global search when the searched record number doesn't comply with the number prefix defined in sys_number table - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Exact search is not working with New global search when the searched record number doesn't comply with the number prefix defined in sys_number table
KB0687065

Exact search is not working with New global search when the searched record number doesn't comply with the number prefix defined in sys_number table


1913 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Description

Exact search is not working with New global search (Jakarta release onwards) when the searched record number does not comply with the number prefix defined in sys_number table. This used to work in the Legacy global search.

Steps to Reproduce

  1. Log on to any out of the box Jakarta instance
  2. Navigate to change_request.list
  3. Open any change record, for example CHG0000004
  4. Modify the change number from CHG0000004 to ECR0000004 and save the record
  5. Search for ECR0000004 in global search
  6. User is presented with search results page $sn_global_search_results.do

Note:

  • If we setup a prefix in sys_number table for ECR, then above search works. In some scenarios, the customer wants to have many prefixes for the same table and in that case, there cannot have more than one prefix in sys_number table.
  • Exact search used to work as expected in legacy global search

Workaround

This issue is under review. You can subscribe to this known error article (click the Subscribe button at the top of the article) to receive notifications when more information is available about this issue.

 


Related Problem: PRB1244245

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.