I have a property exposed as a column on my work table. This property is a propety embedded within a page property. The page property is set to auto populated by copying from a data page.
I have a report definition that is displaying this exposed column. When I run the report definition it seems to be attempting to auto populate the property again. How can I avoid this? The parameters being passed to the data page are not populated at this time. All I want is to just display the value in the exposed column. It looks like this is causing an error in ApplyColumnConfig to occur where an index is out of range because of the auto population. It does in the end however display the value in the exposed column but I can see in tracer it is attempting to auto populate. I believe this is affecting performance of the report definition as well. So how can I avoid this auto population from being attempting when running a report definition?
***Edited by Moderator Marissa to update Content Type from Discussion to Question***