Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Data page reference interpreted as string literal



Report Definition rules do not require a developer to specify the class of a data page used for filtering on the Pages & Classes tab. However, if a data page is referenced but not added to the Pages & Classes tab then the data page reference is interpreted as a string literal by the engine.

Error Messages

Not Applicable.

Steps to Reproduce

  1. On any Pega 7.2 system create a report definition in the PegaSample class.
  2. Add .pyID as a column.
  3. Add a filter with a data page reference like: .pxObjClass Contains Declare_AppExplorerData.pyAppExplorerWorkPool.
  4. Run the report and review results.

Root Cause

The engine interprets the filter expression as a string literal if the data page is not included on the pages and classes tab of the rule form.  


In this example, adding "Declare_AppExplorerData" / "Code-Pega-List" to the Pages & Classes tab resolves the issue.

A product enhancement to provide a guardrail warning for this issue is being considered by product management. 


Published July 28, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us