In Constellation, filtering is generally not supported on a List View column whose value is only derived on the client side by a Response Data Transform on a Data Page. When the Data Page is sourced from a Data Transform, the results are already materialized on the client, so promoted/end-user filters are not sent back to Pega for server-side evaluation.
The best practice is to make the field a real, queryable data attribute in the data source itself, rather than deriving it only in the Response Data Transform. If you need users to filter by that field, calculate and persist it earlier in the data flow, or use a Report Definition / queryable Data Page with Allow query so the filter can be pushed into the data request and then optionally enriched afterward in the response Data Transform.
- Move the logic into the source query or Report Definition, so the column exists before the list is rendered.
- Store the derived value in the underlying data type or class, then expose it as a normal list column.
- If the derivation must remain in a Response Data Transform, use it only for display, not for filterable fields, because Constellation filtering won’t reliably work for that column.
Refer to the below forum article for more info on this-