Records are unavailable to view depending on the field on which results are sorted

[Bart Z]

Hello guys,
depending on the field that I am sorting, the records are present or not -> the total amount doesn't change

Here are two screenshots, any ideas what can be the cause?:

[Ryan82]

We're experiencing the exact same issue.  It seems to happen when querying the CMDB with a filter element being a custom field and the first sort element being Name.  If you add another sort in front of name like "domain", then you might be able to get your records to appear.

[Daniel Oderbolz]

We also have the same issue. I suggest that you open a support case for this.

Most likely, an index is missing. 

Check in the syslog and you will likely see something like 

Syntax Error or Access Rule Violation detected by database ((conn=...) Key 'wzibnxkr_for_table_cleaner' doesn't exist in table 'cmdb_par10')

In our case it seems to be a missing index, but we are currently waiting for the fix to be implemented by SN.

[webyork]

Did anyone get a resolution to this. We are in the process of upgrading to Xanadu. And any data housed in cmdb table is affected by similar issue.

We try to sort by sys_updated_on and the data becomes unavailable to view, change the sort column and the data is visible again.

Out case with ServiceNow has got us to add in 2 database indexes from the tables and columns area. But while these are now indexed we are still having the issue.

Any further insight appreciated.

[Kevin Peppers]

We are also in the process of upgrading to Xanadu. And any data housed in cmdb table is affected by similar issue.

Sorts by sys_updated_on and the data becomes unavailable to view, change the sort column and the data is visible again.

We also have another set of instances that we have not upgraded to Next experience and that set of instances does not seem have the issue. 

[webyork]

We got a resolution by getting the index rebuilt in the tables & columns listing for cmdb_ci. For some reason the index needed to be in a specific order, the system felt it existed so I was blocked from doing it myself but via a case we had the index removed? and readded and it fixed the issue when we moved to Xanadu. I am unsure of the specifics to the fix, but by getting the index built for the columns of issue in a specific order it allowed the data to visualise.