Passing Parameters Between ReportViewers Controls

  • I'm having difficulty in Passing parameters in-between two ReportViewer Control on separate web pages. In simple words, I've created two Reports in Visual Studio (1. Sales Top Level Summary, 2 Sales by Month) where Sales Top level summary report is a RS Matrix Report which show's sales total in each month and by clicking on each financial month manager's can view the sales details in each month. Now this work perfectly fine when I preview these reports in Visual Studio and then deploy and view in Report Manager

    In second part I've integrated Sales Top level summary report into Asp.net page using Top-Level ReportViewer control and set the ShowToolBar Property to "False" so i can my own CSS setting, this even works fine here and i can view the sales summary in each month using this page, because I set Navigation as Jump to report and then passing FinYear and FinMonth as parameters to Sales By Month Report. Here is the snapshot of my sales top level report

    Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar

    2008/09 64 59 58 73 70 55 80 79 72 61 74 64

    2009/10 69 65 59

    Now my problem is since i have ShowToolBar Property to "False" the ShowExportControl Property is not visible on the Sales by Month report as I'm using the same ReportViewer control to view this report. To Solve this I've created another Asp.net page with Another ReportViewer control which is linked to the Monthly sales report, but I'm not sure how to pass the FinYear and FinMonth parameters to other ReportViewer control on 2nd Asp page, I did tried Jump to URL "http://localhost/BI/Sales_Monthly_Report.aspx" but that didn’t work either..

    Any help in this regard will be highly appreciated...

  • Hi,

    I have never tried this solution. but have you tried to add any event for the reportviewer control.

    Reportviewer control has events like DrillThrough which occurs when the user drills down to a subreport. There i think the toolbar visibility should be able to set true.

    So it would not require another page for the sub reprt also.

    Thanks

  • I m agree with the above solution it will be easier to handle at the ASP.Net Page itself rather than calling it for different page.

    And this is common requirement which need to be taken care from ASP Code itself.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply