Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Michael Fede (MichaelF4652) Raytheon Technologies
Raytheon Technologies
US
MichaelF4652 Member since 2016 17 posts
Raytheon Technologies
Posted: Nov 6, 2018
Last activity: Nov 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?

To see attachments, please log in.
Pega Platform Low-Code App Development Reporting

Posted: 5 years ago
Posted: 13 Nov 2018 16:11 EST
Michael Fede (MichaelF4652) Raytheon Technologies
Raytheon Technologies
US

Thank you for the suggestion. When I went back to try this I checked the guardrail warnings again and the warnings about properties needing to be optimized were gone. Not sure what caused this issue to be resolved. 

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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