Passing a parameter via URL to SQL Server Reporting Services

First, be sure to replace Reports/Pages/Report.aspx?ItemPath= with ReportServer?. In other words, instead of this:

http://server/Reports/Pages/Report.aspx?ItemPath=/ReportFolder/ReportSubfolder/ReportName

Use this syntax:

http://server/ReportServer?/ReportFolder/ReportSubfolder/ReportName

Parameters can be referenced or displayed in a report using @ParameterName, whether they’re set in the report or in the URL. You can attach parameters to the URL with &ParameterName=Value.

To hide the toolbar where parameters are displayed, add &rc:Toolbar=false to the URL (reference).

Putting that together, you can run a URL with embedded values, or call this as an action from one report and read by another report:

http://server.domain.com/ReportServer?/ReportFolder1/ReportSubfolder1/ReportName&UserID=ABC123&rc:Toolbar=false

In the report’s dataset properties query: SELECT stuff FROM view WHERE User = @UserID

In the report, set the expression value to [UserID] (or =Fields!UserID.Value)

Keep in mind that if a report has multiple parameters, you might need to include all parameters in the URL, even if blank, depending on how your dataset query is written. That means repeating the parameter name for multiple values of the same parameter, too.

To pass a parameter using Action = Go to URL, set expression to:

="http://server.domain.com/ReportServer?/ReportFolder1/ReportSubfolder1/ReportName&UserID="
 &Fields!UserID.Value 
 &"&rc:Toolbar=false"
 &"&rs:ClearSession=True"

Be sure to have a space after an expression if followed by & (a line break is isn’t enough). No space is required before an expression. This method can pass a parameter but does not hide it as it is visible in the URL.

If you don’t include &rs:ClearSession=True then the report won’t refresh until browser session cache is cleared.

To pass a parameter using Action = Go to report:

  • Specify the report
  • Add parameter(s) to run the report
  • Add parameter(s) you wish to pass (the parameters need to be defined in the destination report, so to my knowledge you can’t use URL-specific commands such as rc:toolbar using this method); however, I suppose it would be possible to read or set the Prompt User checkbox, as seen in reporting sever parameters, through custom code in the report)

For reference, see this page on URL encoding, e.g. / = %2f

Browse More Popular Posts

Leave a Comment