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.
The "is not" filter is excluding records with empty values from the query output - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • The "is not" filter is excluding records with empty values from the query output
KB0596161

The "is not" filter is excluding records with empty values from the query output


11249 Views Last updated : Oct 16, 2023 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Description

Using the "is not" operator when filtering out certain values in a choice or reference fields field (for example, subcategory on incident), results in subcategory with empty value being filtered out along with all records that fit the condition.

 

Steps to Reproduce

 

  1. Navigate to Incident > Open.
  2. Click the menu icon .
  3. Select Group by > Category.
  4. Check the results.
  5. Expand the filter.
  6. Add condition [Category] [is not] [Database].
  7. Check results.
    Notice the Database category and the empty results were filtered out.

    See also use case in PRB659408/KB0680079

Workaround

This is expected behaviour for modern databases such as MySQL, SQL Server, and Oracle. The way the "not equal to" operator is behaving in the SN platform is congruent with standards-compliant SQL dialect.
 
Additional information on the SQL operator can be found in the stackoverflow article Not equal <> != operator on NULL  
 
The query will need to have two conditions in OR: <field> is not <value> OR <field> is empty.

 


Related Problem: PRB688991

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.