Hi All, In Pega Constellation UI, we are using a List View sourced from a Data Page. One of the columns in the list is populated via a Response Data Transform applied on the Data Page.
However, the filter functionality is not working for this specific column.
Question
Is filtering supported in Constellation List Views for columns whose values are derived or populated through a Response Data Transform on a Data Page?
If not, what is the recommended approach to enable filtering for such derived fields in Constellation?
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-
This is intended by design on the fields populated through response data transform. The filter trigger the DXAPI & in turn changed to a SQL query behind the scenes as below.
SELECT “PC0”.“merchantname” AS “MerchantName” , “PC0”.“transactionid” AS “TransactionID” , “PC0”.“pyguid” AS “pyGUID” FROM pegadata.pr_abc_personal_data_transacti “PC0” WHERE ( ( ( UPPER(“PC0”.“merchantname”) IN (? , ? , ? ) ) ) ) ORDER BY 3 ASC
I tried a similar scenario. I have a Response Data Transform on a Data Page that uses a “For Each Page In Primary.pxResults” loop and explicitly sets a derived value as a named property (.ClinicalID) on each result page, and I was able to successfully filter on that column in the Constellation List View.
Could you share more details about your configuration? Specifically:
How exactly is the derived value being set in your Response Data Transform?
Is it being mapped at the individual result page level or at the Data Page level?
What property type is the column bound to in your List View?
This might help narrow down why filtering isn’t working in your case.
The requirement is straightforward from a reporting and data sourcing perspective. The report is configured to retrieve case-level information using a Data Page as the source, where the underlying data retrieval mechanism is implemented through a Report Definition (RD).
All case-related attributes are sourced directly from the primary case class through the RD. For the “Assigned To” column, the value is derived using associations configured within the Report Definition to resolve assignment information from the corresponding assignment tables.
Based on the assignment type and context, the association dynamically joins either:
Assign-Worklist for operator-based assignments, or
Assign-Workbasket for queue/workbasket-based assignments.
with the below Response Data transform setting the “Assigned To user” value.
