Global Search fails on Data Page-backed List View when PropertyRead Access Control Policy is configured on a property

User Experience
1

We are facing an issue in Pega 25.1.2 (Constellation).

We have configured a PropertyRead Access Control Policy (Full Mask) on the TransactionReference property for external users.

  • The property is masked correctly in the List View.
  • However, when the List View is backed by a Data Page, performing Global Search throws the following error:

A ReadProperty access control policy is defined on property ‘TransactionReference’. This property can be displayed, but it cannot be used to filter, sort, group, or rank query results, or in SQL functions.

Interestingly, the same PropertyRead Property works without any issue in other scenario where we have configured query with list of records, and Global Search works as expected.

Not Working for list view:

image
image1837×504 71.1 KB

Working for Query property with list of records:

image

Access Control Policy Cofiguration:

image
image1090×272 32.9 KB

Access Control Policy Condition:

image
image1091×277 32.2 KB

Is this expected behavior or a known limitation? Has anyone faced a similar issue or found a workaround?

2

In your Data Page-backed List View configuration, remove TransactionReference from the list of searchable or filterable columns used by Global Search. When Global Search runs against a Data Page-backed List View, Pega attempts to use all visible columns as filter criteria in the underlying query, which conflicts with the PropertyRead Access Control Policy (Full Mask) on that property. Since the policy blocks the property from being used in query filtering, sorting, or grouping, the search fails. By excluding TransactionReference from the searchable columns in the List View settings, Global Search will no longer try to filter on it, eliminating the error. The property will still display as masked in the view for external users, and Global Search will continue to work normally using the remaining columns.