This project is read-only.

Description

This ExtReportViewer webpart contains Microsoft.Reporting.WebForms.ReportViewer inside it and is intended to be used by SharePoint Foundation with Reporting Services run in Native mode.

The main advantage of the ExtReportViewer over a standard Microsoft ReportViewer plug-in with both Native and Integrated SSRS is in its sophisticated connection interfaces.

The ExtReportViewer can be both a consumer and a provider for other linked reports of the same type and allows creating report chain where one main report supplies valid parameters to a number of other secondary reports.
Such cluster can be the best solution when the report parameters are of a query type and are dependent on each other.

The ExtReportViewer can also be a consumer for multiple HTML Form webparts. It can even receive parameters from SPList and after that to be updated from HTML Form. HTML Form parameters always override List parameters.

For example, in this image the Main report receives parameters from the SPList and at the same time sends parameters to other 2 slave reports. In addition to it both slave reports receive local updates from HTML Forms.

 

The report URL and Path are specified from WebPart's Editor Area.
The reports physically can be located in either SharePoint list or SSRS directory.

For example:

  • SSRS directory:
    • ReportURL - http://serverhost:8020/ReportServer
    • ReportPath - /Reports/myreport
  • SharePoint List:
    • ReportUrl - http://serverhost:8020/ReportServer
    • ReportPath - http://serverhost/Reports/myreport.rdl

 

The ExtReportViewer writes trace messages to SharePoint ULS logs at category - SharePoint Foundation/Web Parts.

The ExtReportViewer supports all types of report parameters, like: Text, Number, Date, as well as multiple and nullable values.

Pre-installation configurations and troubleshooting:

Report Viewer Toolbar does not render properly on IIS 7.0 http://blogs.msdn.com/b/webtopics/archive/2009/02/10/report-viewer-toolbar-does-not-render-properly-on-iis-7-0.aspx
The type 'Microsoft.SharePoint.Portal.Analytics.UI.ReportViewerMessage's cannot be found http://www.net-aspect.com/blog/using-the-report-viewer-asp.net-control-in-a-custom-developed-sharepoint-web-part
In remote mode, the Report Viewer control requires session state be enabled or Report Server connection information specified in the config file http://www.elumenotion.com/Blog/Lists/Posts/Post.aspx?ID=123
The Report Viewer Web Control HTTP Handler has not been registered in the application's web.config file. http://www.net-aspect.com/blog/using-the-report-viewer-asp.net-control-in-a-custom-developed-sharepoint-web-part

Appendices

 

  • HTML Form webparts allow connecting only one field to one report parameter at a time.
    If you have a number of report parameters you have to place a separate HTML Form per parameter.
  • Because of one well known bug/feature, when ReportViewer executes SetParameters method it forces to rerender the whole page which on the other hand invokes back rerender event for ReportViewer webpart with SetParameters method. It leads to infinite rerender. To avoid that, the SetParameters method in webpart’s rerender event is not executed when there is no change in report parameters.
    So, clicking on HTML Form submit button when there is no parameter change is senseless.

Last edited Apr 3, 2013 at 7:47 AM by MarkBabayev, version 8