"Cannot filter by field [status] because it is a complex, multiple, or chil

Hi - Does anyone know if the following limitation still applies in Appian? --? 'applying filters using a column in the child CDT is currently not available for cases where there is a one to many relationship between parent and child' 

The behavior has not changed since this original post was made. What is your use case for performing this kind of filter?

Hi Peter Lewis I have a use case for a customization to campuspass/workforse safety application. We would like to filter incidents by user role, I was able to attach the user.role cdt to the incident cdt to make incident.user.role and use it in the record to display it in the grid. Unfortunately the filter does not work as a user can have multiple roles. When I try to filter by incident.user.role.roleId it fails with the same complex/multiple error. 

Hi Peter Lewis I have a use case for a customization to campuspass/workforse safety application. We would like to filter incidents by user role, I was able to attach the user.role cdt to the incident cdt to make incident.user.role and use it in the record to display it in the grid. Unfortunately the filter does not work as a user can have multiple roles. When I try to filter by incident.user.role.roleId it fails with the same complex/multiple error. 

Yeah unfortunately the the best way to address this would likely involve either adding a database view for this filter or nesting your data in the opposite direction (i.e. M:1 or 1:1 relationship). 

Hi,

In case you are choosing to create a database view, avoid combining too many child tables in a single view depending on your requirement. Best will be, in the DB view, limit it to just 1 parent table (One) and 1 child table (Many), so that the result set is generated without tasking the DB for performance.