Hi,
I've got a master-detail report much like you're invoice example.
The subreport has a reportparameter which I then set to a field in the mainreport. So far so good.
But if I then add a filter to the mainreport the report doesn't work anymore, the parts in main are displayed correctly but in the subreport area I get a red text saying:
An error has occurred while processing Report ":
Method GetRowsByStringGuid(System.RuntimeType strGuid) not found.
I use entitydatasource as my datasource and the parameter is actually a guid so I have todo some manual conversion as guid's are not supported.
The strange thing I've noticed however is that if I specify a value for the parameter in the subreport in the ReportParameter Collection Editor like 0 which is not guid but still a valid string. The report works as expected again.
Is this by design or am I missing something or maybe I found a bug?
I'm looking forward to hearing from you.
Tomas
2 Answers, 1 is accepted
The provided information is insufficient for us to determine what exactly might be at fault here. If the report stops working after you've added a filter to it, then most likely it has to do with the filter, so elaborating on what you filter and what does the filter expression depends might lead you to the culprit.
The detail report works properly after you set a default value for the param, as most likely the report value does not get pulled from the master in a first place.
If you're still having problems, please provide more information on your scenario or better provide us with a runnable sample report and once we review it, we would be able to advise you.
All the best,
Steve
the Telerik team
Rank 1
Thank you for your answer. After posting this I changed my datasource for the subreport to use a SQLDatasource instead and it started working as expected. Today I again tried to find out the cause of the error I was getting and it looks like it's some kind of designer error because once I run the report everything is ok in the SIlverlight reportviewer and when I return to the designer then the data is there as well.
However if I then restart Visual Studio and try to preview the report in the designer I get the same error message again but running the report again solves the problem, is the data somehow cached and that's why it works after actually running the report?
But as I said I've moved to SQLDatasource and I think I will stick with that so not a big problem for me I just wanted to let you know.
If you still want a running example I might be able to provide one for you later this week.
Tomas