ASP.NET ReportViewer as a child of a child control does not work correctly RRS feed

  • Question

  • We have a problem that surfaces with both the 2008 and 2010b2 versions of the Report Viewer control.  Basically, we end up with broken postbacks if the report viewer is in a custom control, which is itself added to the page.  In other words, the Report Viewer is a grandchild control; CreateChildControls on the page creates rvControl, and rvControl.CreateChildControls creates the report viewer.

    In the case of the 2008 control, the document map button forces a postback, and loses its state.

    In the case of the 2010b2 control, the page goes into an infinite postback loop.

    In both cases it works if we disable async rendering, although of course lots of other things such as paging break.

    This is a major problem for us right now - any ideas?
    Monday, November 2, 2009 4:58 PM