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

Report definition displays warning for exposed columns



Two new fields are added in a report definition and the properties are exposed through the Optimization Wizard. When the application is packaged and moved to other environments, a Moderate level Guardrail warning occurs in the report definition. Though the physical columns exist in the database, the system does not recognize the exposed columns.

Error Messages



These properties are not optimized: <property_name>. Displaying them may result in poor performance. Consult your system administrator about optimizing properties for reporting.

Steps to Reproduce

  1. Create new embedded properties.
  2. Add the new properties to an existing report definition.
  3. Expose the new properties.
  4. Package the rule changes and move to another environment.

Root Cause

When packaging is performed for rule changes, the class rule is not included. This is where external mappings are mentioned for the exposed embedded properties.


Perform the following local-change:

Package the class rule in the Product rule since external mappings are in the class rules for the exposed embedded properties.

Published August 19, 2019 - Updated December 2, 2021

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