Reporting Services 2005 and jump-to report navigation

Hi, I have used Jump-To report navigation in RS 2000 successfully to
navigate from one report to another, passing a report parameter to the
second report from a click event from a table in the parent report.
However, when I try to do the same thing in RS 2005, when I set up the
navigation jump-to report, the form picks up the report I want to
jump-to, but not any of the report parameters.
Has anyone found this problem and has anyone solved it?
I am using the April CTP install of Business Intelligence Studio
(Client Tools) connecting to an April CTP of Yukon on another server.
Thanks for any helpI believe we saw this issue and fixed it in the upcoming CTP15(June). I
tried a simple JumpTo report with CTP15 using a parameter and it works fine.
--
| From: "MDXQuery" <imgroup1@.hotmail.com>
| Newsgroups: microsoft.public.sqlserver.reportingsvcs
| Subject: Reporting Services 2005 and jump-to report navigation
| Date: 31 May 2005 07:31:18 -0700
| Organization: http://groups.google.com
| Lines: 13
| Message-ID: <1117549878.146860.257860@.o13g2000cwo.googlegroups.com>
| NNTP-Posting-Host: 212.135.29.68
| Mime-Version: 1.0
| Content-Type: text/plain; charset="iso-8859-1"
| X-Trace: posting.google.com 1117549883 20456 127.0.0.1 (31 May 2005
14:31:23 GMT)
| X-Complaints-To: groups-abuse@.google.com
| NNTP-Posting-Date: Tue, 31 May 2005 14:31:23 +0000 (UTC)
| User-Agent: G2/0.2
| Complaints-To: groups-abuse@.google.com
| Injection-Info: o13g2000cwo.googlegroups.com; posting-host=212.135.29.68;
| posting-account=BkKmtgwAAAA2HVQbpzZ1Z_YN45g-L9kZ
| Path:
TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed00.sul.t-online.de!t-onli
ne.de!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!postnews.google.com!o1
3g2000cwo.googlegroups.com!not-for-mail
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.reportingsvcs:45004
| X-Tomcat-NG: microsoft.public.sqlserver.reportingsvcs
|
| Hi, I have used Jump-To report navigation in RS 2000 successfully to
| navigate from one report to another, passing a report parameter to the
| second report from a click event from a table in the parent report.
| However, when I try to do the same thing in RS 2005, when I set up the
| navigation jump-to report, the form picks up the report I want to
| jump-to, but not any of the report parameters.
| Has anyone found this problem and has anyone solved it?
|
| I am using the April CTP install of Business Intelligence Studio
| (Client Tools) connecting to an April CTP of Yukon on another server.
|
| Thanks for any help
|
|sql

Reporting Server - Passing Parameters programtically

We've developed several reports where you can type in / select variables and run them, affecting their outcomes.

We'd like to change this so if the user clicks on a link from our Intranet, this takes them straight to the report with the appropriate parameter(s) - rather like the "jump to report" function within a report - i.e. the url for that function...

Is this possible?

Steve

Yes, it is. You should check in the docs for topics mentioning "URL Access", but the basic deal is this:

I usually start this by drilling down to the appropriate URL for the report (sans parameters) using ReportServer rather than Reports (Report Manager) interface.

Once you have the appropriate base URL, you can add the appropriate instructions to the URL's query string.

You start with the ones that tell the server to render the report, in the appropriate format, for example:

&rs:Command=Render&rs:format=EXCEL

... and then you can add your params to this as more name-value pairs in normal querystring style, for example:

&myParam1=53&myKeyValue=SomeToken&myID=965

... okay?

By "start with" and "then", I don't mean that the order of the params and report instructions in the query string is significant, just that I generally think it through in this order, report-owned instructions and then parameters. If you are going to build the URL dynamically at runtime it helps to think about the two groups separately <s>.

>L<

|||

superb! i think the note to add to this is to use the "report server" site not the "reports" site i.e. http://servername/reportserver rather than http://servername/reports

thanks

|||

Yup, that's the way they do it in the docs, and that's the way I've been doing it... one site is the "real" server and the other is just the pretty interactive interface....

>L<

Reporting Server - Passing Parameters programtically

We've developed several reports where you can type in / select variables and run them, affecting their outcomes.

We'd like to change this so if the user clicks on a link from our Intranet, this takes them straight to the report with the appropriate parameter(s) - rather like the "jump to report" function within a report - i.e. the url for that function...

Is this possible?

Steve

Yes, it is. You should check in the docs for topics mentioning "URL Access", but the basic deal is this:

I usually start this by drilling down to the appropriate URL for the report (sans parameters) using ReportServer rather than Reports (Report Manager) interface.

Once you have the appropriate base URL, you can add the appropriate instructions to the URL's query string.

You start with the ones that tell the server to render the report, in the appropriate format, for example:

&rs:Command=Render&rs:format=EXCEL

... and then you can add your params to this as more name-value pairs in normal querystring style, for example:

&myParam1=53&myKeyValue=SomeToken&myID=965

... okay?

By "start with" and "then", I don't mean that the order of the params and report instructions in the query string is significant, just that I generally think it through in this order, report-owned instructions and then parameters. If you are going to build the URL dynamically at runtime it helps to think about the two groups separately <s>.

>L<

|||

superb! i think the note to add to this is to use the "report server" site not the "reports" site i.e. http://servername/reportserver rather than http://servername/reports

thanks

|||

Yup, that's the way they do it in the docs, and that's the way I've been doing it... one site is the "real" server and the other is just the pretty interactive interface....

>L<

|||Thank you for this information. It works perfectly! You saved me a bunch of time!

Reporting Server - Passing Parameters programtically

We've developed several reports where you can type in / select variables and run them, affecting their outcomes.

We'd like to change this so if the user clicks on a link from our Intranet, this takes them straight to the report with the appropriate parameter(s) - rather like the "jump to report" function within a report - i.e. the url for that function...

Is this possible?

Steve

Yes, it is. You should check in the docs for topics mentioning "URL Access", but the basic deal is this:

I usually start this by drilling down to the appropriate URL for the report (sans parameters) using ReportServer rather than Reports (Report Manager) interface.

Once you have the appropriate base URL, you can add the appropriate instructions to the URL's query string.

You start with the ones that tell the server to render the report, in the appropriate format, for example:

&rs:Command=Render&rs:format=EXCEL

... and then you can add your params to this as more name-value pairs in normal querystring style, for example:

&myParam1=53&myKeyValue=SomeToken&myID=965

... okay?

By "start with" and "then", I don't mean that the order of the params and report instructions in the query string is significant, just that I generally think it through in this order, report-owned instructions and then parameters. If you are going to build the URL dynamically at runtime it helps to think about the two groups separately <s>.

>L<

|||

superb! i think the note to add to this is to use the "report server" site not the "reports" site i.e. http://servername/reportserver rather than http://servername/reports

thanks

|||

Yup, that's the way they do it in the docs, and that's the way I've been doing it... one site is the "real" server and the other is just the pretty interactive interface....

>L<