Configuration Item List is To Long

JamesLindsay
Giga Guru

When in a list view of Incidents and needing to update the config_item field of the incident, often because it is empty, hitting the search button returns ever CI in the CMDB. How do I limit this to principal CIs? 

3 REPLIES 3

Runjay Patel
Giga Sage

Hi @JamesLindsay ,

 

Check below property and add your table on which you have cmdb_ci field. Filter will auto apply.

RunjayPatel_0-1730820067670.png

 

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.


Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------

 

The list I am looking at is the incident table and it is in that list. It's not possible that I have 1.3 million CIs and all of them are in a Principal Class

JamesLindsay
Giga Guru

In ServiceNow if a class is a principal class do extended classes also become principal classes? It does not appear so. Like cmdb_ci_netgear is a principal class but extended classes like IP Switch do not show to be principal in my instance. A quick glide record query shows that I only have 13K CIs within all 38 of my principal classes. So why does this list open a search window displaying 1.3 million?