Filter condition using Tags do not work in Database View reports causing long running data_table.do transactions from long queries - Known Error

Filter condition using Tags do not work in Database View reports causing long running data_table.do transactions from long queries Description Database view reports do not apply filter conditions using Tags.

When Tags are added to reports on Database Views the label_entry filter for the DB view is incorrectly encoded, causing the system to query the entire database view.

Long running data_table.do transactions get generated with corresponding long running queries in the Database.

Steps to Reproduce

From 'Filter navigator' navigate to Database View 'incident_sla'. Click on 'Try it'. Open any record and tag it with 'hello world'. Navigate back to the Database View and add a Task.tags column to the list view from the list layout. Add the filter condition 'Show/hide filter' with Task.tags has 'hello world'. Observe all records are shown, not performing the filter on Task.tags.

Workaround After carefully considering the severity and frequency of the issue, and the cost and risk of attempting a fix, it has been decided to not address this issue in any current or near future releases. We do not make this decision lightly, and we apologise for any inconvenience.

Records with label_entry values must be removed, as label_entry values are not supported for Database Views:

1) Retrieve the long running query from the Database and determine which view this is coming from. The best way to find this is to see which tables are joining and in which order.

2) Navigate to System Definition -> Database Views and find the view that joins on the same tables as the query.

3) Find the offending label_entry records in the instance, or in the database for very large size tables:

3.1) Instance: navigate to label_entry.filter and search for where Table =

3.2) Database: in standby DBI run pbrun snow query --timeout-seconds=9999 "select * from label_entry where label_entry.table = ' "

4) Verify that the urls of the found label_entry records have an encoded sys_id field which does not work for querying the view. e.g. incident_metric.do?sys_id=__ENC__ <-- value should just be a sys_id.

5) Remove the label_entry records.