SSRS Subreport won't run - reporting-services

I have an SSRS subreport that is passed a variety of parameters from the parent report. Some of these parameters are visible in the subreport's parameter list and some are hidden. There are also two additional data parameters are not passed from the parent. These need to be manually selected to actually run the subreport.
The issue is this: when I pass info into the report by clicking on the hyperlink in the parent report, the report will not run inside BIDS. Instead the parameter portion of the report appears to refresh. If I click the View Report button again, it will do the same thing.
The parent and subreport work fine though on the Report Server.
Also, if I use the subreport by itself in BIDS or the Report Server, the subreport will run just fine.
I'm at a bit of a loss to understand what is happening here. Any insight is greatly appreciated.

Related

Cannot see dropdown for "use this report as a subreport" option

I am trying to use a subreport in my master report (local). However, I don't see a dropdown to select the subreport but instead see a textbox. Relative path doesn't work either. What am I missing here?
Note: It is mandatory for me that both master and subreport must be in different folders.
Thanks!

How Can I avoid Blank pages from SSRS PDF files?

Am creating One report project. Where am having one normal report named (Report1.rdl) and one sub report named (Report2.rdl).
Am calling the main report in side the sub report five times by passing values through parameters. So I have five parameters as well. when parameter value is 0 then respective report will not show in the sub report. But thing is that when am doing this am getting blank pages at the end and between the pages as well.
So can You please help me With this. I have already checked with the sizes and clear designing of the main report.
You are 'calling' the reports in the incorrect order.
Main reports 'call' sub reports, not the the way you have it at the moment. Therefore you need to embed the sub-report inside the Main report. As detailed here on MSDN:
"A subreport is a report item that displays another report inside the
body of a main report. Conceptually, a subreport is similar to a frame
in a Web page. It is used to embed a report within a report."

SSRS report with subreports: layout weird when deployed to report manager

I am using a subreport (say 'child1') to create one master report (say 'parent1'). The report 'parent1' uses 15 instances of report 'child1', once for each parameter.
Up untill 10 instances, report behaviour is nice, but once I add an 11th instance, report format is getting weird. I have set Interactive Height to 0 for both 'child1' and 'parent1' reports. I am not sure what I'm missing here.
I have created the report in BIDS 2005, and it's working fine in BIDS. The problem only shows up when deployed in report manager. Also: exporting to Excel and PDF works just fine.
Any input on this is appreciated.
This issue is usually found when the report is deployed to the Report server.
You do one thing, use rectangle container for each sub report & then try out. Might help you out.

SSRS Drillthrough server report error

I have a SSRS report with an action on a text-box.
Go to report property is set to the parent report so this makes the parent report also a drillthrough report for itself.
I deployed the report on the report server and it is rendered ok and also the drillthrough action works ok in the Report Manager.
When I attach this report to a ReportViewer control in an .aspx the parent report is rendered ok but the drillthrough action causes an error (Invalid argument).
I have 2 visible and 3 hidden parameters for this report.
I tried to override the ReportViewerCtrl_Drillthrough event and added the following code:
ReportViewerCtrl.ServerReport.SetParameters(reportParamList);
ReportViewerCtrl.ServerReport.Refresh();
where reportParamList is a list of parameters passed from the parent report to the drillthrough report but I get the same error (I used DrillthroughEventArgs.Report.GetParameters() to get the list of parameters and they're passed by in a correct way).
I didn't find on other forums something like this related to reports deployed on Server Report (only for local report).
Any idea would be very much appreciated!
I have found the issue for this.
It was related to the way .aspx page was built.
My report viewer control was framed by a form tag but it appears it also needed a table tag too.
So this is how my .aspx page looks now:
table
tr
td
form
ReportViewer Control
/form
/td
/tr
/table

ReportViewer Web Control and Dynamic Connection Strings

So I have a report in Reporting Services 2005. In it is one parameter (ConnectionString) which determines which data source the report will use. It also has several other parameters which are dropdown lists derived from the data source chosen in the ConnectionString parameter.
In Report Manager, this works great. All of the dropdowns are greyed out at the beginning. When you choose your data source, the page requeries/repaints and all of the available parameter values for the other parameters are filled in based on the queries for those fields.
However ...
In the ReportViewer web control, when the report is first loaded up, instead of dropdown boxes all of the other parameter fields are just empty textboxes. Choosing a different data source for the ConnectionString parameter doesn't requery/repaint the other parameters.
I've been flipping through the ReportViewer programming reference to see if there's some way to replicate the Report Manager's way of reloading the webpage with the report viewer upon certain parameter changes, but I can't find anything there that isn't over my poor little .NET head.
Any ideas?
Not sure if this is any help but I do have a suggestion. I would try pulling the logic for dropdown boxes out of the report and put them in an ASP.net page. Then pass the parameters to the report and control the rendering/refreshing.
HTH
UPDATE: So it turns out you must provide a default value for any parameters which in turn affect other parameters in your report in order to get the dropdown box to load properly on initialization. Also note this is recursive - so if you have a parameter which affects another parameter which affects another parameter, both the first and second parameter must have default values.