question Re: Records are unavailable to view depending on the field on which results are sorted in Common Service Data Model forum

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

Bart Z — Thu, 05 May 2022 09:48:39 GMT

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?:

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

SebastianKunzke — Thu, 05 May 2022 12:47:56 GMT

Are you sure you are allowed to see all objects of this table?

For me it looks like, that somehow your company deactivated the ACL message "Number of rows removed from this list by Security constraints". Because of that you think, there are no objects, but you just not allowed to see them.

So please check with your admin, if there are any ACLs on this table.

That is a screenshot with a valid ACL message.

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

Hitoshi Ozawa — Fri, 06 May 2022 00:57:30 GMT

Hi Bartłomiej,

Sorting by different rows shouldn't change number of records that are displayed.

Is this happening only when records are sorted by column "Name" or does this happen when sorted by other columns such as "Asset" and "Assigned to"?

Also like to make sure. The records are sorted by clicking on the column header.

Does this also happen when the sort order is selected from the "Add Sort" in filter condition?

Finally, is this an actual table or a database view?

https://docs.servicenow.com/en-US/bundle/sandiego-platform-administration/page/use/reporting/concept/c_DatabaseViews.html

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

Bart Z — Fri, 06 May 2022 05:37:02 GMT

When using other columns than name, operational status, status, and updated -> everything works fine.

When I don't have query for u_sap_system.u_etd_monitoring=true also there is no trouble with filtering by name, or status.

Using the 'Add Sort' functionality doesn't change anything.

It is an actual table.

The column u_sap_system.u_etd_monitoring is the only foreign column here, so maybe it can be the cause?

However, when I move to SAP System table, then I can easily use that query and there is no problem with any sorting

SSo I think that's not a cause of any ACLs

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

Bart Z — Fri, 06 May 2022 05:41:29 GMT

checked, it is not a cause of security constrains

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

Ryan82 — Fri, 01 Dec 2023 17:21:02 GMT

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.

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

Daniel Oderbolz — Fri, 17 May 2024 12:20:51 GMT

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.

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

webyork — Mon, 14 Oct 2024 20:43:35 GMT

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.

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

Kevin Peppers — Wed, 13 Nov 2024 13:45:25 GMT

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.

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

webyork — Wed, 13 Nov 2024 14:28:07 GMT

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.