|
|
You're in the
sql server reporting services
group:Passing parameters thru query string not working
sql server reporting services:
I've got some Reporting Services reports that I'd like to be able to link to
from other dynamic web pages, passing parameters in through the HTTP GET query string. Everything I've read seems to indicate that if I append "&name=value" to the URL, it will load the report with the parameter set to that value. However, my experience has been that it does not. I've tried encoding the ampersand as &, I've tried setting up a form to pass the value in via GET and POST, I've tried moving the parameter to the beginning of the querystring.... Nothing seems to work, I still get a blank report with a prompt for the parameter. (The report works fine when I hand the parameter in manually.) Does anyone have experience with this behavior, or have ideas on how to resolve it? This feels like a bug, and it's dramatically reducing the usefulness of RS for our company. In case it matters, we're running RS on SBS 2003 and designing reports in Microsoft Visual Basic .NET, .NET Framework 1.1.4322 SP1, Development Environment 7.1.3088. It's a little harder to get version numbers for RS
It is not a bug. There are two ways you can create the URL. Both ways will
pull up the report but only one way will fill the parameter values in. On Monday I will post with the correct URL for you to use. Until then, one thing to make sure of is that you are matching your parameter exactly, it is case sensitive. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "richyoung" <richyoung@discussions.microsoft.com> wrote in message news:CA827DA5-CBB0-40FB-AE8E-7BD63C4AEB9A@microsoft.com... > I've got some Reporting Services reports that I'd like to be able to link > to > from other dynamic web pages, passing parameters in through the HTTP GET > query string. Everything I've read seems to indicate that if I append > "&name=value" to the URL, it will load the report with the parameter set > to > that value. However, my experience has been that it does not. > I've tried encoding the ampersand as &, I've tried setting up a form > to > pass the value in via GET and POST, I've tried moving the parameter to the > beginning of the querystring.... Nothing seems to work, I still get a > blank > report with a prompt for the parameter. (The report works fine when I > hand > the parameter in manually.) Does anyone have experience with this > behavior, > or have ideas on how to resolve it? This feels like a bug, and it's > dramatically reducing the usefulness of RS for our company. > In case it matters, we're running RS on SBS 2003 and designing reports in > Microsoft Visual Basic .NET, .NET Framework 1.1.4322 SP1, Development > Environment 7.1.3088. It's a little harder to get version numbers for RS > itself, but if anyone thinks it might matter, I can do so.
Take my solution and add it to a link in a report. Then look at the URL
generated when you execute it. What you want to do is definitely possible. I can take a jump to URL link from my report, click on it and then copy the URL from the address bar of IE. Do this to see how you should be assembling the URL. -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "richyoung" <richyoung@discussions.microsoft.com> wrote in message news:7881CC3F-31D6-4922-81AE-F3C6F779D1BA@microsoft.com... > Bruce- > Thanks for taking the time to reply. The problem you're addressing is a > good fix , but unfortunately it's not aimed at the problem I'm having. I > should have been more clear; the situation I'm using involves linking to a > report from a standard web page on a different server. So I'm > constructing > my urls like so:<br> > http://www.url.com/Reports/Pages/Report.aspx?ItemPath=/path/to/the/report&pid=1234 > <br>where the "pid=1234" thing is the parameter I'm trying to pass in, > named "pid" and expecting an integer value. > <br> > What I get is the report page with a blank prompt for the "pid" parameter, > instead of a report run against that parameter. As I mentioned before, > I've tried it with slashes and with "%2F" encoding for the slashes; I've > tried it with and without the "ItemPath=" segment, etc. About the only > thing > that *does* work for me is linking from one report to another via the > "jump > to a report" property in the Navigation tabs of my objects. I can even > load > the (blank) report page in a browser, manually add the "&pid=1234" or > "&pid=1234" string to the end (thereby guaranteeing that I'm not doing > anything wrong to the rest of the URL), hit enter, and still get a blank > report with a prompt for that parameter. > <br> > I've seen the same failure to import query-string parameters in several > different reports, and I'm at that uncomfortably familiar stage where I'm > feeling 85% certainty that it's not anything I'm doing wrong, and 15% > suspicion that I'm still overlooking something stupid and obvious. > <br> > Does that jog any ideas about what I might need to do to fix this? Thanks > in > advance for any help you might be able to provide, as well as your efforts > so > far. > > --Rich > > "Bruce L-C [MVP]" wrote: > >> The below example specifies the directory starting from the root. I have >> this because this particular report can reside in a different directory >> than >> the report I am jumping to. If it is in the same directory you can just >> not >> worry about specifying the directory. A couple of others things to note, >> I >> use the globals variable so this will work regardless of where I deploy >> it. >> Also, note that parameter values are case sensitive so you must match it >> exactly or you will end up without values in your parameter fields. Also >> note that you can add to this URL a command to tell it to hide the >> parameter >> toolbar. Anyway, this should get you started. >> >> =Globals!ReportServerUrl & "?/Inventory/Similar Loads&Manifest=" & >> Fields!manifstdocno.Value &"&WasteIDNum=" & Fields!wasteidnum.Value >> >> >> -- >> Bruce Loehle-Conger >> MVP SQL Server Reporting Services >>
The below example specifies the directory starting from the root. I have
this because this particular report can reside in a different directory than the report I am jumping to. If it is in the same directory you can just not worry about specifying the directory. A couple of others things to note, I use the globals variable so this will work regardless of where I deploy it. Also, note that parameter values are case sensitive so you must match it exactly or you will end up without values in your parameter fields. Also note that you can add to this URL a command to tell it to hide the parameter toolbar. Anyway, this should get you started. =Globals!ReportServerUrl & "?/Inventory/Similar Loads&Manifest=" & Fields!manifstdocno.Value &"&WasteIDNum=" & Fields!wasteidnum.Value -- Bruce Loehle-Conger MVP SQL Server Reporting Services [quoted text, click to view] "richyoung" <richyoung@discussions.microsoft.com> wrote in message news:CA827DA5-CBB0-40FB-AE8E-7BD63C4AEB9A@microsoft.com... > I've got some Reporting Services reports that I'd like to be able to link to > from other dynamic web pages, passing parameters in through the HTTP GET > query string. Everything I've read seems to indicate that if I append > "&name=value" to the URL, it will load the report with the parameter set to > that value. However, my experience has been that it does not. > I've tried encoding the ampersand as &, I've tried setting up a form to > pass the value in via GET and POST, I've tried moving the parameter to the > beginning of the querystring.... Nothing seems to work, I still get a blank > report with a prompt for the parameter. (The report works fine when I hand > the parameter in manually.) Does anyone have experience with this behavior, > or have ideas on how to resolve it? This feels like a bug, and it's > dramatically reducing the usefulness of RS for our company. > In case it matters, we're running RS on SBS 2003 and designing reports in > Microsoft Visual Basic .NET, .NET Framework 1.1.4322 SP1, Development > Environment 7.1.3088. It's a little harder to get version numbers for RS > itself, but if anyone thinks it might matter, I can do so.
Bruce-
Thanks for taking the time to reply. The problem you're addressing is a good fix , but unfortunately it's not aimed at the problem I'm having. I should have been more clear; the situation I'm using involves linking to a report from a standard web page on a different server. So I'm constructing my urls like so:<br> http://www.url.com/Reports/Pages/Report.aspx?ItemPath=/path/to/the/report&pid=1234 <br>where the "pid=1234" thing is the parameter I'm trying to pass in, named "pid" and expecting an integer value. <br> What I get is the report page with a blank prompt for the "pid" parameter, instead of a report run against that parameter. As I mentioned before, I've tried it with slashes and with "%2F" encoding for the slashes; I've tried it with and without the "ItemPath=" segment, etc. About the only thing that *does* work for me is linking from one report to another via the "jump to a report" property in the Navigation tabs of my objects. I can even load the (blank) report page in a browser, manually add the "&pid=1234" or "&pid=1234" string to the end (thereby guaranteeing that I'm not doing anything wrong to the rest of the URL), hit enter, and still get a blank report with a prompt for that parameter. <br> I've seen the same failure to import query-string parameters in several different reports, and I'm at that uncomfortably familiar stage where I'm feeling 85% certainty that it's not anything I'm doing wrong, and 15% suspicion that I'm still overlooking something stupid and obvious. <br> Does that jog any ideas about what I might need to do to fix this? Thanks in advance for any help you might be able to provide, as well as your efforts so far. --Rich [quoted text, click to view] "Bruce L-C [MVP]" wrote:
> The below example specifies the directory starting from the root. I have > this because this particular report can reside in a different directory than > the report I am jumping to. If it is in the same directory you can just not > worry about specifying the directory. A couple of others things to note, I > use the globals variable so this will work regardless of where I deploy it. > Also, note that parameter values are case sensitive so you must match it > exactly or you will end up without values in your parameter fields. Also > note that you can add to this URL a command to tell it to hide the parameter > toolbar. Anyway, this should get you started. > > =Globals!ReportServerUrl & "?/Inventory/Similar Loads&Manifest=" & > Fields!manifstdocno.Value &"&WasteIDNum=" & Fields!wasteidnum.Value > > > -- > Bruce Loehle-Conger > MVP SQL Server Reporting Services
Use http://www.url.com/ReportServer to run reports. The /Reports
application is the Report Manager, and is not the place to go for URL access. You can look up "URL access" in the BOL for more info, but this will fix your problem with passing in parameters. Ted [quoted text, click to view] richyoung wrote:
> Bruce- > Thanks for taking the time to reply. The problem you're addressing is a > good fix , but unfortunately it's not aimed at the problem I'm having. I > should have been more clear; the situation I'm using involves linking to a > report from a standard web page on a different server. So I'm constructing > my urls like so:<br> > http://www.url.com/Reports/Pages/Report.aspx?ItemPath=/path/to/the/report&pid=1234 > <br>where the "pid=1234" thing is the parameter I'm trying to pass in, > named "pid" and expecting an integer value. > <br>
Bingo! That did it, thanks, Ted. The final form of the url was:
http://www.url.com/ReportServer/Pages/Report.aspx?%2fpath%2fto%2freport&rs:Command=Render&pid=1234 --Rich [quoted text, click to view] "Ted K" wrote:
> Use http://www.url.com/ReportServer to run reports. The /Reports > application is the Report Manager, and is not the place to go for URL > access. You can look up "URL access" in the BOL for more info, but > this will fix your problem with passing in parameters. > > Ted > > richyoung wrote: > > Bruce- > > Thanks for taking the time to reply. The problem you're addressing > is a > > good fix , but unfortunately it's not aimed at the problem I'm > having. I > > should have been more clear; the situation I'm using involves linking > to a > > report from a standard web page on a different server. So I'm > constructing > > my urls like so:<br> > > > http://www.url.com/Reports/Pages/Report.aspx?ItemPath=/path/to/the/report&pid=1234 > > <br>where the "pid=1234" thing is the parameter I'm trying to pass > in, > > named "pid" and expecting an integer value. > > <br> >
Thanks for the post Ted, I had the exact same problem and this worked
wonderfully!! Brian [quoted text, click to view] "Ted K" wrote:
> Use http://www.url.com/ReportServer to run reports. The /Reports > application is the Report Manager, and is not the place to go for URL > access. You can look up "URL access" in the BOL for more info, but > this will fix your problem with passing in parameters. > > Ted > > richyoung wrote: > > Bruce- > > Thanks for taking the time to reply. The problem you're addressing > is a > > good fix , but unfortunately it's not aimed at the problem I'm > having. I > > should have been more clear; the situation I'm using involves linking > to a > > report from a standard web page on a different server. So I'm > constructing > > my urls like so:<br> > > > http://www.url.com/Reports/Pages/Report.aspx?ItemPath=/path/to/the/report&pid=1234 > > <br>where the "pid=1234" thing is the parameter I'm trying to pass > in, > > named "pid" and expecting an integer value. > > <br> >
Wow!!!
Worked for me too. Thanks a lot! Vivran [quoted text, click to view] "Brian" wrote:
> Thanks for the post Ted, I had the exact same problem and this worked > wonderfully!! > > Brian > > > "Ted K" wrote: > > > Use http://www.url.com/ReportServer to run reports. The /Reports > > application is the Report Manager, and is not the place to go for URL > > access. You can look up "URL access" in the BOL for more info, but > > this will fix your problem with passing in parameters. > > > > Ted > > > > richyoung wrote: > > > Bruce- > > > Thanks for taking the time to reply. The problem you're addressing > > is a > > > good fix , but unfortunately it's not aimed at the problem I'm > > having. I > > > should have been more clear; the situation I'm using involves linking > > to a > > > report from a standard web page on a different server. So I'm > > constructing > > > my urls like so:<br> > > > > > http://www.url.com/Reports/Pages/Report.aspx?ItemPath=/path/to/the/report&pid=1234 > > > <br>where the "pid=1234" thing is the parameter I'm trying to pass > > in, > > > named "pid" and expecting an integer value. > > > <br> > >
Greetings all,
Thanks to 'Ted K' for his solution regarding the way to address a reporting server via URL. ....Also thanks to 'richyoung' for putting a scenario similar to mine into words. Here's my expanded scenario: I am using ASP.NET 2.0 and have a bulleted list object of displaytype hyperlink. the hyperlink values are stored in a SQL Server2000 and represent paths to individual ReportServer items. Using Ted K's path construction. My problem is how do I capture a selected parameter value from the active Aspx page and concatenate it to the end of the querystring parameter upon clicking any bulletlisted hyperlink? I hope my question is clear. Thanks all -- Application Engineer / DBA UCLA SOM [quoted text, click to view] "Ted K" wrote:
> Use http://www.url.com/ReportServer to run reports. The /Reports > application is the Report Manager, and is not the place to go for URL > access. You can look up "URL access" in the BOL for more info, but > this will fix your problem with passing in parameters. > > Ted > > richyoung wrote: > > Bruce- > > Thanks for taking the time to reply. The problem you're addressing > is a > > good fix , but unfortunately it's not aimed at the problem I'm > having. I > > should have been more clear; the situation I'm using involves linking > to a > > report from a standard web page on a different server. So I'm > constructing > > my urls like so:<br> > > > http://www.url.com/Reports/Pages/Report.aspx?ItemPath=/path/to/the/report&pid=1234 > > <br>where the "pid=1234" thing is the parameter I'm trying to pass > in, > > named "pid" and expecting an integer value. > > <br> >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |