Filter: 'fieldname' is not empty, shows empty fields

Not applicable

‎05-26-2009 01:04 AM

Hi, for quite some time I have been looking for ways to clean up some tables.
When we first started our SMS integration a lot of redundant records were imported. I'd like to get rid of them. (table cleanup plugin does not really work)

I created some scripts to delete records that have empty names or asset_tags. But somehow a big part of them or skipped by the script.

To troubleshoot I filtered the records in a list (table cmdb_ci) and add the following filter:

asset_tag isnot empty, but in the result list you can still see asset_tags that are empty. I noticed this as well on a lot of other tables and fields (SEE ATTACHEMENT for an example)

Can anyone explain this behavior?

0 Helpfuls
  • 2,431 Views
3 REPLIES 3

Julian Hoch
ServiceNow Employee
ServiceNow Employee

‎02-12-2015 08:22 AM

ServiceNow makes a distinction between blank values and NULL values, this might be the problem in your case (see also https://hi.service-now.com/kb_view_customer.do?sysparm_article=KB0522773). So this is basically a known bug.


Raja50
Giga Contributor
In response to Julian Hoch

‎05-30-2018 06:51 AM

Hello, 

Is this bug have been corrected? 

I need to filter (empty) document ID from metric_instance, but I can't do that

Can you help pls? 

Regards 

0 Helpfuls

mbeaver
Tera Contributor
In response to Julian Hoch

‎03-17-2023 08:38 AM

don't know if you still work at SN but just in case. I logged in to my SN account but still don't have access to the article. In any case the same data in Dev and Test environments gives different search results. I am able to filter out empty records in Dev but not in Test. 

0 Helpfuls