Link to home
Start Free TrialLog in
Avatar of gberkeley
gberkeley

asked on

(How) Does Report Builder Handle "Drill-Through" Reporting?

I am coming to you gurus with a problem I can’t get past.  I keep running into an error (see screenshot below).  I am trying to create a drillthrough report and subreport.  Each time I set the path to another report I get this error.  I am not sure what I am doing wrong or if my permissions are restricting me from accessing two reports at the same time.  I am working on creating summary reports that will point to other reports for more details if needed and do not want to use drilldowns as it would leave too many empty placeholders for printing a summary page.  Any help would be wonderful.
Report-Builder-Error-041212.png
ASKER CERTIFIED SOLUTION
Avatar of TempDBA
TempDBA
Flag of India image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of gberkeley
gberkeley

ASKER

Good places to check!!! Will take a look and confirm.
UPDATE 4/16:
I was able to get a subreport to display in the main report.  The subreport was a copy of the main report (renamed) and pulled from the same dataset.  As soon as I started to play with the parameters the error code appeared again.

I do not have any nulls in the report (main or sub/drillthrough).

I am able to run the reports individually.

I will continue to play with this a little today.  I think I am getting close.  I am going to create a drillthrough report and main report with limited info for testing purposes using the same dataset.  It may have to do with folder structure/permissions.  I intend to maintain all datasets and reports within the same folder for the testing.  

Any thoughts on this most welcome.  BTW - we are using SharePoint 2010 as "front end" for report runners, and Report Builder as "Back end" design studio,
We checked and validated that permissions were not the issue, and then with some playing around, we discovered that - THE PARAMETER NAMES IN THE SUBREPORT ARE CASE SENSITIVE.  Strange but true.   Now we can get the sub report to run. In classic MSFT fashion, we still get the same error at run time, but it actually runs and returns the desired results as well.   THANKS SO MUCH for your help with this and for your responsiveness.