Is exposing a property to multiple tables a best or recommended practice?
I have seen the below solution in posts but have not seen if this is Pega recommended or best practice:
Question: How do i optimize a parent class property which is visible in sub class through inheritance.
PS: Parent and Child classes point to different tables
Answer: 1) Create a same property in the child class with same as parent class. Optimize and delete the property from the child class. (Preferred approach).
NCS Pte. Ltd
SG
Hi @DavidH85: It is not recommended to duplicate the data in multiple tables unless you have a specific need (like reporting) which cannot be achieved using links / joins.
With regards to optimization, i dont think there is a need to create duplicate property in the child class because when you try to optimize the property in parent class, it will give you options to select the child class too
Thanks.