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

How to optimize a property in a production level system



After migrating an exposed property to a higher environment, the associated column is not populating and reports are not recognizing the property as exposed.

Error Messages

Not Applicable

Steps to Reproduce

In the higher environment, look for the property and list view where it gives the warning that property is not optimized.

Root Cause

A software use or operation error where the Data-Admin-DB-Table instances associated with the table the property was exposed in were not included in the Rule-Admin-Product export.


Perform the following local-change: Include the Data-Admin-DB-Table instances for the table with the exposed property in the Rule-Admin-Product export and re-deploy it into a higher environment.  After doing so, the column populator utility can be used to back fill the column for any pre-existing instances of the associated class if necessary.


Published October 25, 2016 - Updated October 8, 2020

Was this useful?

100% 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