Since migration to 11.0.17.222 I have had problems linking master/child type reports. I have several reports which consist of a "master" report with one or more "child" reports in it.
The "child" reports exist in the "group footer" sections for respective groups found on the master report. Prior to the 11.0.17.222 migration using a report parameter of "= ReportItem.DataObject.Fund" resulted in a parameter "Fund" being made available for consumption by the "child" report. As of the 11.0.17.222 migration this is passed into the "needs data source" event (of the child report) as null 100% of the time.
As a work around for the problem, I have re-written my "needs datasource" events to use the "ProcessingElement" value and access the bound data element from the ".DataObject.RawData". This seems to be working although I suspect it is probably a "non-supported" means of resolving this apparent bug.
A sample of what I am doing is as follows:
var rowData = qd.DataObject.RawData as BudgetDataLibrary.SumRevenueByFundData;
if ((rowData != null) &&
(string.IsNullOrWhiteSpace(rowData.Fund) == false))
{
parentFund = rowData.Fund;
}
3 Answers, 1 is accepted
There are changes in the way properties are read as of R3 2016 - Changes on items in report events are not applied.
Please test modifying sub reports to be bound to the main report's data object via expressions - How to bind Sub Report to Main Report's Data.
If you need further help, please post the code used in events and details about the used events.
Regards,
Stef
Telerik by Progress
Rank 1
Iron
Veteran
Iron
While I thank you for your reply, it does nothing to answer my question. What has changed.
Using a report that has run for over two years, upon application of the latest Q's framework the existing report began failing to run. As noted in your documentation, I used the expression "= ReportItem.DataObject.Fund" (Fund being a field found in the parent master reports data source). This expression was used in the child reports parameters when the sub report was embedded into the master report. Again, that formula has been used multiple years (and worked). As of this Q's framework the value returned by that expression is 100% null despite the parent having data in its values.
The work around I posted in my prior message has allowed me to repair the "broken" report despite the continuation of the, as documented, usage of the dataobject continuing to be used and failing to produce valid values.
Again, what has changed? Did I find a bug? As your documentation states that I am doing things correctly, I am at a loss to explain the observed results.
I cannot say for sure which change in the report processing caused the issue with the existing reports in your application. The hierarchy displayed in the Report Explorer and the data structure are important when you get data for nested data items. Also there are changes in the way properties are read and how complex items in report can be accessed during the processing.
The best approach to troubleshoot the problem is to have locally demo reports and details about the last version in which they worked as expected in your tests. Please feel free to post the code for generating the reports here, or open a support ticket and send us the code in a ZIP file, including test data or the data model used by reports.
Thank you for your understanding.
Regards,
Stef
Telerik by Progress