I think the cleanest approach would be to use a single Date Picker or Date Range component and store the userβs selection in variables. We can then reference those variables in the PQL filter logic across all three date fields.
The typical setup would be:
-
One Date Picker/Date Range component in the View
-
Store the selected values in variables such as start_date and end_date
-
Apply a custom filter condition that checks all three date columns against those variables
For example:
FILTER
"table"."date_1" >= {t ${start_date}}
AND "table"."date_1" <= {t ${end_date}}
AND
"table"."date_2" >= {t ${start_date}}
AND "table"."date_2" <= {t ${end_date}}
AND
"table"."date_3" >= {t ${start_date}}
AND "table"."date_3" <= {t ${end_date}}
This should allow one date selection to drive the filtering for all three date fields, rather than having separate date filters for each column.