Custom control and setup of SSRS report parameters from a web page

By:   |   Comments (6)   |   Related: > Reporting Services Parameters


I have a ASP.NET web application that I would like to present SQL Server Reporting Services reports in. I understand that reports can be rendered using the ReportViewer control, but the interface for parameters is a little bland and doesn't match our site colors. Is there a way that report parameters can be passed to the Report Services instance without having to use the Reporting Services parameter prompts?


Luckily, there is a fairly straightforward way of passing report parameters to the Reporting Services instance. Let's say we have a web site that tracks the hourly weather observations of a number of airports in the area. We can offer a report using Reporting Services that will allow the users to select a site, a start date, and an end date for the observations they want to see. Once you open Visual Studio 2005 and the page you want to add the report to, you'll see a ReportViewer control in the Data tab of the toolbox.

Location of the ReportViewer control in Visual Studio 2005

Once you have installed the ReportViewer control (or see it in the Data tab of the toolbox), you can start building the page. For this example I create a simple page with three text boxes, two image buttons to control the calendars and a link button that will pass the parameters and render the report:

Web page used to collect parameters

In addition to the controls above, I dragged a ReportViewer control onto the page while in Design mode. The benefit to dragging it over in Design mode is that the reference to the Microsoft.Reporting.WebForms namespace is automatically added to the page. Once the control is on the page, the rest of the work is done using either Visual Basic or C# (this example will use Visual Basic). One setting you can add to the ReportViewer control in Design or HTML mode is the Processing Mode. The ReportViewer control can render reports from a local source, called a Client Report Definition File, or RDLC. They can also render reports from a remote source, like a SQL Server Reporting Services instance. In this case, we have a Reporting Services instance available to us, so we will use the remote processing mode:

HTML code where the processing mode is indicated

Now that we have the ReportViewer control in the page and the general layout taken care of, we can write the code that fires when the View report link button is clicked. First we declare a generic list of report parameters. This involves both the System.Collections.Generic namespace as well as the Microsoft.Reporting.WebForms namespace. On the SQL Server Reporting Services report there are three parameters: SiteID, StartDate, and EndDate. You'll also notice in the code below that we use the actual report server URL (like ""), not the Report Manager URL (""). We then add a report parameter for each one to the generic list of parameters and specify the report path. The ServerReport.SetParameters function is used to apply the report parameters specified in the generic list to the actual report parameters on the Reporting Services report:

Code for Passing Report Parameters to the Reporting Services Instance

Protected Sub cmdGetReport_Click(ByVal sender As Object, ByVal e As System.EventArgs) Handles cmdGetReport.Click 
Dim colRP As New System.Collections.Generic.List(Of Microsoft.Reporting.WebForms.ReportParameter) 
colRP.Add(New Microsoft.Reporting.WebForms.ReportParameter("SiteID", UCase(txtSiteID.Text.Trim))) 
If IsDate(txtStartDate.Text.Trim) Then 
      Dim dteStart As Date = txtStartDate.Text.Trim 
      colRP.Add(New Microsoft.Reporting.WebForms.ReportParameter("StartDate", Right("0" & dteStart.Month, 2) & "/" & _ 
     Right("0" & dteStart.Day, 2) & "/" & dteStart.Year)) 
End If 
If IsDate(txtEndDate.Text.Trim) Then 
     Dim dteEnd As Date = txtEndDate.Text.Trim 
     colRP.Add(New Microsoft.Reporting.WebForms.ReportParameter("EndDate", Right("0" & dteEnd.Month, 2) & "/" & _ 
     Right("0" & dteEnd.Day, 2) & "/" & dteEnd.Year)) 
End If 
rvWeather.ServerReport.ReportServerUrl = New Uri("$SQL2K5") 
     rvWeather.ServerReport.ReportPath = "/Weather/Site Report" 
     rvWeather.Visible = True 
End Sub 

When the user reaches the page, all they have to do is enter the parameters they want and click the View Report button:

Specifying the criteria in the web application
The report generated after applying the report parameters
Next Steps

sql server categories

sql server webinars

subscribe to mssqltips

sql server tutorials

sql server white papers

next tip

About the author
MSSQLTips author Tim Cullen Tim Cullen has been working in the IT industry since 2003 and currently works as a SQL Server Reports Developer.

This author pledges the content of this article is based on professional experience and not AI generated.

View all my tips

Comments For This Article

Monday, May 9, 2022 - 4:11:06 PM - Carlos A Back To Top (90072)
This is Great! How can update code to render direct to excel and not display the report in the web page.

Wednesday, December 3, 2014 - 7:06:52 AM - Ramu Back To Top (35475)


 We are having few issues with SSRS reports when we click on any report it prompts to add "Compatibility Mode" should be enable and it is working fine. however i do not want to use "Compatibility Mode" for IE 9 so are there any parameters can be set in browser or ssrs report viewer URL as my clients users should not use compatibility mode and all the reports should work.


Thanks in advance.



Friday, November 15, 2013 - 5:52:39 PM - daguyse Back To Top (27515)

zaboomafoo this is a great way to do this

Thursday, October 14, 2010 - 12:16:26 PM - Tim Cullen Back To Top (10271)
In the situation I based the tip on there were a number of multi-valued parameters and I used AJAX ( to handle the callbacks for the ones that were dependent on the selected value.  You can concatenate all of the selected values, pass it as one of the report and stored procedure parameters, and have SQL parse the string (see this tip for how to do that:  That would avoid having to use dynamic SQL in the stored procedure.  

If you're going to use AJAX keep in mind that the Report Viewer control will have to reside outside of the Update panel that the parameter fields are located, since at the time the tip was published the Report Viewer control did not work properly inside an Update Panel.  Please post if you news on your next attempt-good or bad news!

Thursday, October 14, 2010 - 9:09:42 AM - Tatyana Back To Top (10269)
I am totally with Oded Dror (who posted a question above).  The method described in the article could lead a way to a solution to a problem of a page being refreshed on each parameter selection in the report. When there is a number of multivalue parameters in a report, and each of them is depeneding on a previous one, the page refreshement becomes very irritating and time consuming issue. It seems that moving parameters from report into the application could do a trick. It's just I don't know how to deal with multivalue parameters in the application :) I'll try to find it out, but if anyone knows the answer please share it.

Thanks, -


Tuesday, August 18, 2009 - 8:02:16 AM - odeddror Back To Top (3905)

Hi there,

My question is lets assume that the siteid is like that

Select siteid from my table where siteid in(@siteid) - multi value

(in reporting services you will get a drop down list with multi select option)

How do you set your  dropdown list control to pick more than one siteid and pass these into  sql server?

one value it easy the problems begin when it multi value (I did not see any example of multi values with dropdown list control)


Oded Dror


get free sql tips
agree to terms