Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Limitation on page-correlated filters

Updated on May 11, 2022

When you use Report Definition filters that search the indexes, multiple filter conditions referencing properties in the same page list or page group might not return the expected results. The following example illustrates this limitation.

Example: PegaSample has a page list pyProductList that has an embedded page list ProductInventoryList that includes pyCountryName.

Assume the following sample data:

.pyID : S-1
.pyProductList(1).pyProductName = “Prod A”
.pyProductList(1).ProductInventoryList(1).pyCountryName = “India”
.pyProductList(1).ProductInventoryList(2).pyCountryName = “United States”
.pyProductList(1).ProductInventoryList(3).pyCountryName = “United Kingdom”
.pyProductList(2).pyProductName = “Prod B”
.pyProductList(2).ProductInventoryList(1).pyCountryName = “Egypt”
.pyProductList(2).ProductInventoryList(2).pyCountryName = “France”
.pyProductList(2).ProductInventoryList(3).pyCountryName = “Australia”

S-1 is returned in the results when the following filter is specified in the Report Definition: .pyProductList(1).ProductInventoryList(1).pyCountryName CONTAINS “France”.

Note that the indexes for the page lists are ignored when applying the filter, so S-1 matches the filter even though France is a value in ProductInventoryList(2), and not in ProductInventoryList(1). Filters on values in page lists and page groups function as any filters.

You can search for a work object when any of the products has inventory in country “France." You cannot search for a work object where product “Prod A” has inventory in “France.”

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us