In your scenario the data is visualized by two separate sub reports. Thus synchronizing the layout of the distinct templates or exchanging information between the data scopes of the sub reports is not supported via expressions.
Our suggestions in your support ticket on the same question are as follows:
Only Page Sections are ignored when a report is rendered in a SubReport item. Thus in the sub report you can add a ReportFooterSection or static group (without specified grouping field) and use the built-in Data functions e.g. Exec, to get the required total in the newly produced sections. The report is data driven template and Data functions can be used in header and footer sections as long as the provided data scope is correct.
Since mixing data scopes of different sub reports is not supported, you can use your data model to display related information between sub reports:
- Expose properties getting the needed calculations from the data model and use them as fields directly;
- Avoid passing the scope as a string from the data model. Any change in the reports layout will cause you troubles. Instead use directly the name of the scopes in expressions.
- To have synchronized sections/items sizes between reports format the data. For example synchronize the string length of two properties used as fields in the different reports, and customize the report templates to have the same sizes for the visualizing items.
If you need further help, let us continue the discussion in the support ticket regarding these questions in order to avoid splitting details between the threads.
Thank you for your understanding.
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.