Question

3
Replies
1227
Views
Michael Fede (MichaelF4652)
Raytheon Technologies

Raytheon Technologies
US
MichaelF4652 Member since 2016 17 posts
Raytheon Technologies
Posted: November 6, 2018
Last activity: November 13, 2018
Posted: 6 Nov 2018 17:17 EST
Last activity: 13 Nov 2018 17:12 EST
Closed

How to resolve "Not optimized for reporting" warning for properties in Single Page?

In Pega 7.4 I have a report definition which is using properties from a Single Page property. I've run the Optimize for reporting wizard for these properties, but we still have the guardrail warnings on the report definition.

I can see that it added Column name to Property name mappings on the class and can see those columns on the table directly in the database. I don't see the columns listed when I look at the Database Modify Schema wizard.

Is there an additional step to optimize these properties? Is there a bug with this guardrail warning? Do I need to submit an SR to address this?

Pega Platform Low-Code App Development Reporting
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.