Use two fields of the same type as filters

Introduction

Let’s see how to use two fields of the same type as filters on a list without creating conflict.

Before you start

Have a list page, with two page filters based on the User aggregate. In our example, we are using a list of Tickets and filtering it by “Assignee” and “Reporter”.  Each of those filter components should be set to “aggregate type” with the data pointing towards “user” (attribute tab). The list component should have a behavior “applicable page filters” of type “ticket” with the fields “Assignee” and “reporter”.

Leaving the setup unchanged causes issues because when an Assignee value is selected, the system applies the filter to both the Assignee and Reporter fields. Since both filters are of the same type, the system cannot distinguish between them, leading to incorrect filtering.

Step-by-step instruction

1. Filter key on page filter

Add a filter key (attribute tab) to each page filters and give them a unique value. In this example, the field's name was used as the filter key for its corresponding page filter.

2. Applicable page filters

Two applicable page filters must be set on the list, one for each field, using the same filter key previously assigned.

Conclusion

With these adjustments, the filters now work independently—selecting an Assignee will only filter by Assignee, and selecting a Reporter will only filter by Reporter. This eliminates conflicts and ensures accurate filtering on the ticket list.