checked, it is not a cause of security constrains

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...

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

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.

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.