We have a requirement to optimize a property which is inherited from parent class.
We have created a page property in our work class, and the page definition is Org-FW-DivFW-Data-ABC. We have property "propOne" in Org-FW-DivFW-Data. Since this property "propOne" is inherited it is not shown in App explorer of work class. We have a requirement to optimize this property since it is being used in report definition.
Since this property is not shown in App explorer, we are not able to optimize this property. If we open the property directly and try to optimize it, we are not able to see the work class in the 'Optimized for classes' list in the Property Optimization tool. If we could have seen the inherited property also in the app explorer, we could have optimized the property without any issues.
Could you enable the Debug for DB queries in the tracer setting and provide the tracer file of the use case for our further investigation, also share the full stack trace of the error from the log file.
Even though you do the changes at the database level, we are not sure about the engine code how it will act on those changes. Moreover this kind of requirement is not supported by Pega as per the information from product specialists due to some side effects.