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

The 'Optimize for reporting' option does not work as expected



'Optimize for reporting' option does not work correctly. The user is able to optimize the same property the second time.

Error Messages

Not Applicable.

Steps to Reproduce

  1. Select a property and navigate to the Actions tab
  2. Click the 'Optimize for reporting' option
  3. Verify the schema whether the column is created or not
  4. Perform a property optimization for the same property

Root Cause

An issue in the custom application code or rules.


Here’s the explanation for the reported behavior: 

The user was optimizing a property from the class group which is at the Framework layer. In the optimization wizard, all the frame work classes associated to the class group are displayed with the associated database table. Additionally, another set of implementation classes are also displayed along with the associated database table. Hence, the user can select the table in which they want the property to be optimized. For example, if the user selects one table form the displayed list of tables, the property is optimized in the selected table and is mapped to the associated classes. 

On clicking the 'Optimize for reporting' option again, opens the optimization wizard and displays the remaining tables in which the property can be optimized. Thus, the same property can be optimized in different tables.


Published July 23, 2018 - 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