If you are using a Landingpage and showing a list with Promoted filters, your options are limited for getting to the correct results, since the param.pySearchPageName will be empty.
If your datapage is using a datatransform as a source, all datapage results will be on the client and filtering is done client-side. This means no filter data will be send to Pega and you won’t be able to do modifications on filtering at runtime.
If your datapage is using a report definition as a source (and using ‘Allow querying’), every filter value change by the end-user will cause a refresh of the datapage and its results. The filters will be parsed on a dynamically set *dataRequest *pagename. This page can be used in the response-datatransform configured in the datapage (make sure Pass parameters is set to true) which is run after the report definition is run. Here you can enrich or delete data whichever you like.
The name of the dynamically set dataRequest pagename can be found in parameter param.pyImplicitParameter .
In the response datatransform, you want to handle parameter param.pyImplicitParameter which can have a value like
{“dataAPI”: {“dataAPIRequestPage”: “dataRequest_O6ZRF” }}
Here is a short example of how to map such a thi ng.
In the tracer you will see that this data request page looks as follows (in this example there was a property ‘Title’ and I filtered on the letter ‘k’:
Above is the summary of my answer to the question below, and is (at least) applicable to Pega 25.1.2:
Related topics
- Empty List on Load in Constellation Landing page shows how to do this using REST implementation
Enjoyed this article?
See suggested articles from our Constellation 101 series and view all our Knowledge Shares from our User Experience Expert Circle.