So if you run your report definition with tracer on and DB Query and DB Cache events enabled, you don't see a SQL query event to retrieve the results from the database?

Does your report also contains Group property ?

I still haven't figured a way to get around this. Any help is appreciated.

How is the data page being loaded?

Is the issue here that the value you are getting for Group.GroupID is different from the value in the worktable, or just that you don't want the data page to be invoked when you run the report?

I think this is a defect and you need to raise an SR. I'm able to replicate this issue and I see an obvious ramification of this. In my case, I created an autopopulated property with "copy from data page" option. The data page has internal data table as data source. I used OOTB D_pyProduct as the data page. When the case is created, based on the entered GUID, the corresponding product details are "copied" over into the case and persisted. When the product details are exposed and used in a report definition, and you run the report, the data page is reloaded. So if data in the data table was modified after it was "copied" over to the case, the RD output now shows the latest data and not the data as it was saved with the case. In other words, the behavior is the same as what you expect when you use "refer to a data page" and not "copy from data page". If you open the case from the RD output, the clipboard shows the correct, expected data. So the issue IMO is that the data page on the autopopulated property shouldn't get triggered while running the RD.