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?
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.