Hi Joon-Sae,

I want to elaborate a bit on the issue and also announce its resolution:

First, the original issue appears because the used Binding to the property actually modifies the report definition (e.g., Property path: ReportSource.ReportDocument.DataSource, which is a smart workaround to directly pass data to the inner report). This however has stopped working with the introduction of an optimization of the definition properties' values reading back in 2016. Since then, for such a Binding that changes the definition to work as before, one needs to turn off this optimization using the respective configuration setting. However, we do not recommend turning off this optimization as it would impact performance. Note that this optimization can now be turned off on a single report level as well (see the referenced above article).

Second, the good news. Based on your approach we realized how useful it is to be able to pass data from the main report to the child report. That is why now, with release R3 2022 SP1 we introduce a DataSource property on the SubReport item. It allows passing data to the inner report either with a Binding like: Property path: DataSource, Expression: = Fields.Details or using any supported data source component. Please, give it a try. With this introduction, we consider this issue resolved.

Regards,
Milen
Product Manager for Progress Telerik Reporting & Progress Telerik Report Server

Hi Joon-Sae,

The status of the item is still Unplanned. Basically, we prioritize the items based on the number of votes and some other aspects. Note that once there is an update on it, you will get a notification.

Regards,
Neli
Progress Telerik