Subclass Properties Incorrectly Detected
Posted: Thu May 12, 2011 9:38 am
We are passing a fairly complex data model to the reporting engine. One of the traits of our data model is that the properties on the passed object may be sub-classed of the object type of the property. If this is the case, these properties are cast as the property's object type, hiding any additional attributes on them
For example,
Say we want to report on a list of books.
Books have authors and authors may be one of two classes: Class Author, or subclassed NovelAuthor.
If books have a property for the author of type Author, when they are fed to the report engine the additional attributes on NovelAuthor are not exposed.
This is a simplified example. In our case, we are extending model classes and we can be confident that we will always be passing the subclassed object (Basically we have a base common code model that we add additional properties to based on the project)
Is there any way to force the engine to dynamically determine the properties, rather than examining the type of the property and typecasting to that?
If you run the attached example, open the report and then view the Dictionary, you will notice that when the Author is rolled open, it has only the name Property. Desired behaviour is to have both the name and genre properties visible.
For example,
Say we want to report on a list of books.
Books have authors and authors may be one of two classes: Class Author, or subclassed NovelAuthor.
If books have a property for the author of type Author, when they are fed to the report engine the additional attributes on NovelAuthor are not exposed.
This is a simplified example. In our case, we are extending model classes and we can be confident that we will always be passing the subclassed object (Basically we have a base common code model that we add additional properties to based on the project)
Is there any way to force the engine to dynamically determine the properties, rather than examining the type of the property and typecasting to that?
If you run the attached example, open the report and then view the Dictionary, you will notice that when the Author is rolled open, it has only the name Property. Desired behaviour is to have both the name and genre properties visible.