Close popover
Subhajit Chattopadhyay (SubhajitChattopadhya)
Infosys Australia
Lead System Architect
Infosys Australia
SubhajitChattopadhya Member since 2010 36 posts
Infosys Australia
Posted: July 12, 2017
Last activity: July 28, 2017

What is the best practice in exposing an inherited property?


We had a requirement where in our existing application we had many data classes defined where there were properties.

e.g. We had a data class A which had properties X,Y and Z. We have one more data class called B which inherits A and has properties P,Q and R.

Now, we created a Page Property in Work class for B called PageForB which shows the P,Q,R properties and can use the inherited properties X,Y and Z.

We need to build a report where we need to use Y as a reference in context of PageForB.

Directly, we are unable to expose the property Y for PageForB because it does not show it under it(It only shows P,Q and R).

We can create the Y property in the B data class (which will give us a warning that property already exists in parent and can degrade the performance) and can then expose the property for PageForB context in Work class.

If we don't follow the above step, then when we reference the property in Report Definition as PageForB.Y, it gives a warning that the property is not exposed and can degrade performance.

What is the best approach for this requirement? As I know Declare Index is used for embedded PageLists and PageGroups.

Shall I create a declare index and report on that class?

Please suggest



Moderation Team has archived post,
Close popover 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.