Optimize for reporting not working from Actions menu

I stumbled upon what appears to be a little issue with the "Actions > Optimize for reporting" menu item.

In Pega 7.1.6 and possibly other versions, it seems that trying to optimize any single value property from the Property rule's Actions menu results in the following error:

No Valid classes in the hierarchy

Optimization cannot be performed for classes in this hierachy because of one or more of the following reasons : they are abstract or in a Pega shipped ruleset or mapped to either pr_other or an external table

This is not the case. Optimizing this very same property by right-clicking on its name in the App Explorer does jump to the Property Wizard correctly. Why does the former procedure fail?

PS. Where do I formally file a bug report with Pega?

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.


Keep up to date on this post and subscribe to comments

February 26, 2016 - 9:56am

Hi Edgar, I just wanted to let you know that I'm checking with the Reporting team on this issue. Thank you for taking the time to share your experience.

March 7, 2016 - 1:15am
Response to swanm


This issue can be seen only under the below circumstances.

1) If the external table was mapped.

2) If the table was mapped to pr_other.

3) If the table that was mapped does not contains the BLOB Column (pzPvStream).

Also we have not seen any issues in this area.Please send us the "TestConnection" details for this class to further investigate.

Please raise an SR with Pega Support facing an issue other than the mentioned points. 

December 22, 2017 - 12:27pm
Response to Subhakar

Hi Subhakar

Why do we need BLOB while exposing the column from the wizard?

If i m trying to expose directly a column executing the alter statement for the table which doesn't have BLOB in the DB itself, Pega is not identifying that the column is exposed and throwing an error while saving the record in the table. Could you please explain the reason behind this? is Pega keeping track of the Column which is exposed only through wizard. 



December 24, 2017 - 2:07pm
Response to Ambresh.

Hello Ambresh,

In Pega All  the user defined properties saved inside the blob column .

In order to run report definition  columns need to be exposed in the table so property optimisation required here .

BIX also can be used to extract data from the blob .

You can optimise the property directly by right click on property or you can run the column population wizard .

Let me know if you have any other questions.