Drillthrough report with remote processing in web report viewer

I've built a set of drill through reports using the Navigation tab.  I'm rendering the reports via the Reportviewer control in an ASP.NET app (RTM).  To accomlish this do I need to write code in the "Drillthrough" event to set the parameters of the drill through report and change the Report path for the reportviewer control   If so, how do I capture the value from the parent report in order to pass it to the drill through report

Answer this question

Drillthrough report with remote processing in web report viewer

  • nojetlag

    I am having the same problem when trying to drill-through my server reports in remote mode using the ReportViewer control! Does anyone have a solution to this yet
  • DrTrueline

    Like I said, you can opt to use the Jump To URL and trap the Hyperlink event to load a new report in the report viewer.. That works for me..
  • D3lta

    This seems to be a common problem (and one that I have as well!). My scenario is this: I have created a drillthrough report which works properly when used in a winform in remote mode, but will only display itself when used in a webform (as a S Burris described above). The samples provided on gotreportviewer.com work for me as well, but unfortunately the only webforms example uses local reports which do not provide any insight into the remote mode.

    I suspect there is something in web.config or in IIS that needs to be configured, but I cannot find any documentation on this. Any thoughts


  • Marc Moore

    In VS2005 there is no hyperlink event!

  • Iyana

    No, all you have to do in the Drillthrough event handler is supply data.

    In the event handler you can examine parameters being passed from the mainreport to the drillthrough report.

    The path of the drillthrough report is specified in the mainreport's RDLC definition.

  • Augustin Calin

    Any update !

    I am having a similar problem. I am using remote reports and setting the report creditentials via the IReportServerCredentials interface and drillthrough is not working in my application. If I use the default credientials locally (without setting the ReportServerCredentials) it works fine, but this is not an option in the production environment.

    Any thoughts


  • tarmac321

    I'm using remote reports though, not local reports.  I don't have to supply data, the remote report has it's own connections and datasets, I just pass parameters to the report. 

    In the event handler where would I examing the parameters being passed from the main report to the drill through report   Didn't see it in the sender.


  • Robert Nguyen

    Not being successful using drillthrough, I instead used the Jump to URL Navigation to specify the actions I intend to take when a report item is clicked. I just parse the URL in the Hyperlink event of the ReportViewer
  • rfinlay

    I encounter the same behavior but with a local report. I have a drillthrough report event handler but it does not execute when i drill through the report. The web page containing the reportviewer control is being displayed within an Iframe. any updates on this problem
  • Mahoura

    Generally, the problem of the viewer ignoring the user interaction (for drillthrough, toggle, bookmark, or sort) is the result of the viewer thinking that the report definition has changed. Any change to either ServerReport or LocalReport that happens after the LoadViewState event might cause the viewer to get into this state. The most common problem is setting the ReportServerUrl for server mode or report definition for either mode (ReportPath, ReportEmbeddedResource, etc).

    There is a known issue with the viewer that it can be overly sensative to these property changes. For example, it will sometimes think the definition has changed even if you set the ReportServerUrl property to its current value. So it is best to avoid setting these properties on a postback unless you intend to change the report definition.

    Note also that it isn't strictly a report definition change that can cause this problem. If you call SetParameters(), for example, that will cause the report to be reprocessed with the new parameter values. As a result, the viewer will disregard any click from the user since it applied to the old processed report.


  • Paul Woodgate

    In the case of remote reports everything is automatic. There is no need to handle the drillthrough event.

    If you are handling the drillthrough event, then you can inspect the parameters by calling DrillthroughEventArgs.Report.GetParameters().


  • Vhii

    That was my hope, but it's not working correctly in my implementation.  I'm setting the ReportPath and default parameters during Page_Load.  I'm checking for a Postback though and not setting these properties if IsPostback. 

    Currently, when I click to drill through the report viewer just reloads with the starting report and starting parameters. 

  • Scott Fisher

    Yes you just need to avoid setting the parameters on every postback. Depending on the structure of your page, this might be as simple as only setting them when you receive a changed event from your date input control.
  • mcneil_eric

    I use the SetParameters to pass the start date and end date ( dynamic values ) to my report using the querystring and SetParameters. Is there another way of doing this that will allow the drill through to work
    K

  • Drillthrough report with remote processing in web report viewer