Retire policy Filter CI's count is mismatching with count from the platform

nthelapolu
Tera Contributor

Hi All, 

For same filter condition, the CI's count is mis matched from platform and Data manager in ServiceNow.

From Data Manager PFB Screenshot, Count is (21,737).

nthelapolu_0-1784053228970.png

nthelapolu_1-1784053348541.png

From Platform for same condition, it is showing less count(21,585), as shown in below picture.

nthelapolu_2-1784053621122.png

Retirement Custom Definitions:

nthelapolu_3-1784053773172.png

 

Please suggest, what might be the issue?

5 REPLIES 5

Tanushree Maiti
Tera Patron

Hi @nthelapolu 

 

 

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

Hi Tanushree,

It is already set to 'true', please find my last screenshot, in the post.

Vikram Reddy
Tera Guru

Hey @nthelapolu,

 

Line up the Class operator first, because your two screenshots aren't actually running the same filter. In Data Manager the condition reads Class is Computer (exact class match). In the platform list view the condition reads Class is a Computer, which is a hierarchical match on sys_class_path and pulls in every subclass sitting under Computer, not just records where Class literally equals Computer. "is" and "is a" are not interchangeable on the Class field, so the two counts were never guaranteed to agree.

On top of that, your third screenshot shows the real second factor: the Enforced conditions panel. Data Manager ANDs every active row from CMDB Retirement Custom Definitions (Configuration Item and Computer here) onto your filter before it counts Included records. A plain list view has no idea those definitions exist, it only evaluates the condition you typed.

  • Operator: make Class is vs is a consistent on both sides
  • Enforced conditions: copy that panel's logic into the list filter by hand if you want a true apples-to-apples count
  • Breadcrumb noise: "Sys class path is a /!!/!2/!(%" is not corrupted data, it's KB0726377, a known display-only defect that fires whenever a Class "is a" condition renders as sys_class_path in the breadcrumb

 

Thank you,
Vikram Karety
Octigo Solutions INC

Hi Vikram,

Thank you for your response. Could you please clarify, is the Retirement custom definition and Retire policy retire definition I created to retire the CIs of Computer and it's child classes if those are not discovered from past 3 months is correct? or does it required any changes?