Related list condition may not be applyed for a dot walked condition on self referencing TPC child table - Known Error

Related list condition may not be applyed for a dot walked condition on self referencing TPC child table Description Adding a related list condition using a dot walked condition may result in incorrect results with the condition not being applied if:

the condition is set on a table per class child table that has a reference to itself the condition is added by dot walking through the self reference display column on the child table is inherited from the parent table Steps to Reproduce

In this scenario, customer_account extends/is child of sys_user in a table per class hierarchy, and inherits display column from sys_user. The issue is reproducible for any tables that match the pattern described above:

Activate Customer Service plugin if it is not active. Create two records in customer_account and mark them as customer true: Account1, Account2. Create a record in sn_customerservice_case. Select Account1 as account and Service Desk as assignment group. Create a report on sys_user_group. Add Related condition "Greater than or Equal to 1" on Case->Assignment Group. Under "All of these conditions must be met", set condition Account.Parent Account is Account2. Run the report. Notice the wrong number of records returned 1. The expected would be 0. 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.

If possible re-write the condition to avoid the issue, for example in the above steps to reproduce, instead of dot walking to Account.Parent Account, use Account is one of. Dynamic filters may also be used to avoid dot walking in this case.