Reporting Services – problem with passing parameters directly in the URL

In one of the projects I had to create reports (using Reporting Services) that then should be accessible from the application I’ve been developing.

As the first thing I created the reports themselves (RDL files), deployed them using the Report Manager (more often http://localhost/Reports or http://localhost/Reports$SQLExpress), and configured so I could access them. However, each time I accessed a report I had to provide the input parameters which were used by the stored procedure in order to deliver appropriate amount of information. I wanted to avoid that by passing the parameters somwhowin the URL.

Google came with two interesting articles: Using SQL reporting services in an asp.net application with some notes on report parameters, and Passing parameters and other options directly through a URL in Reporting Services. I followed the instructions but failed. In fact I got stuck making minor changes to the URL, checking the configuration, googling further…

It was only my friend who spotted that I tried to pass the parameters to the Report Manager using URL similar to http://localhost/Reports/Pages/Report.aspx?ItemPath=XXX&rs:Command=Render&ParamName=ParamValue. Instead I should use the Report Server, so link looking this way: http://localhost/ReportServer/?XXX&rc:parameters=false&rs:Command=Render&ParamName=ParamValue.

Note: Please remember there are two services: Report Manager and Report Server and understand the difference between them. This way you won’t loose presous time, as I did

17 Responses to “Reporting Services – problem with passing parameters directly in the URL”

Feed for this Entry Trackback Address

1 Dave
August 29, 2008 at 10:08

Thanks for pointing this out – I’ve been unsuccessfully trying to pass parameters and hadn’t noticed this. :-S
2 David K
September 22, 2008 at 19:51

Thanks So much, I was in the middle of frustration whan I found this,
3 Ivano
September 24, 2008 at 10:40

Thanks so much….i tried with this link and it finally work:

http://rs/ReportServer/Pages/ReportViewer.aspx?%2fFolderName%2ReportName&rs%3aCommand=Render&ParamName=ParamValue

Thanks
4 Chintak
October 4, 2008 at 9:59

thanks for pointing out the difference
5 Mark
November 26, 2008 at 19:10

You are a lifesaver! Thanks for posting this information! I was about to lose my mind…
6 John Schofield
November 28, 2008 at 15:44

Thanks a lot trying to sort this out for 3 days
7 max
January 13, 2009 at 15:36

Thank you very much,

Very usefull. We saved a lot of time thx to your comment.

Grt,
8 susan
February 13, 2009 at 2:47

unfortunately I still have a prob.
I use =”javascript:void(window.open(‘http://vmsql03/ReportServer/RequestDetail1?%2fVMSQL03%2fRequestDetail1&rc:parameters=false&rs:Command=Render&RequestID=(Fields!RequestID.Value’))”

my second report doesn’t acknowledge the value from 1st report when I click it.
if I run manually yes…it works fine.
any idea?

Thanks,
9 Mark
September 2, 2009 at 8:42

Thank you. It’s very helpful for me.
10 Mike
October 7, 2009 at 16:42

Thank you! Exactly what I needed.
11 Carrie
October 21, 2009 at 23:03

THANK YOU!! This finally solved my problem!
12 Adam
October 29, 2009 at 14:28

Saved me a lot a time and hassle! Thanks, exactly the information I was looking for.
13 Saugat
October 30, 2009 at 10:50

My report runs in report manager but not in report server, it gives an “internal error”. Please help.
14 Kapil
November 29, 2009 at 13:44

You made my day man. Many thanks!
15 Los
January 6, 2010 at 2:20

Wow, thank you so much! I was going nuts trying to figure this out. Jeez, so simple.
16 kali charan tripathi
January 8, 2010 at 10:35

Please go through given below link>>

http://social.msdn.microsoft.com/Forums/en-US/sqlreportingservices/thread/5c525e46-c47e-4bea-9356-ac93537cb88c