Jump to Report Parameters collapsed

Hi
I am using a jump through report action to call a sub report. The main
report has the paramters displayed but for the sub report the section
where the parameters are displayed is collapsed. Is there a way to
change this behaviour for the second report, my users will want to
know where the parameters are.
A second question, how to you go back to the first report without
coding another jump to report action. In the development environment
(visual studio) there is a nice blue button that you can use to go
back. Once again my users will not want to use the back button on
internet explorer.
I am using SQL 2005 RS with service pack 2 and am displaying the
reports via report viewer control.
ThanksUse Jump to URL instead of jump to report. You have full control over the
URL which includes collapsing or not the parameter area. Read up on URL
integration on Books Online. One option for this is that you can if you want
open up a new window. Then they can just shut down the window when they are
done. Some examples for you of Jump to URL
Jump to URL gives you more control than jump to report.
For the first two examples be careful with the single and double quotes.
Here is an example of a Jump to URL link I use. This causes Excel to come up
with the data in a separate window:
="javascript:void(window.open('" & Globals!ReportServerUrl &
"?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
"&rs:Format=Excel','_blank'))"
This comes up as html (default format) in a separate window
="javascript:void(window.open('" & Globals!ReportServerUrl &
"?/SomeFolder/SomeReport&ParamName=" &
Parameters!ParamName.Value','_blank'))"
If you don't want to have it appear in a new window then do this in jump to
URL:
=Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
Parameters!ParamName.Value
As far as not using the IE back button? Not sure why that is a requirement.
Pretty much everyone know how to do that and if they don't you would have to
train them for an alternative method so train them about the back button.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<trevor.howe@.engenoil.com> wrote in message
news:1191587402.088348.21130@.r29g2000hsg.googlegroups.com...
> Hi
> I am using a jump through report action to call a sub report. The main
> report has the paramters displayed but for the sub report the section
> where the parameters are displayed is collapsed. Is there a way to
> change this behaviour for the second report, my users will want to
> know where the parameters are.
> A second question, how to you go back to the first report without
> coding another jump to report action. In the development environment
> (visual studio) there is a nice blue button that you can use to go
> back. Once again my users will not want to use the back button on
> internet explorer.
> I am using SQL 2005 RS with service pack 2 and am displaying the
> reports via report viewer control.
> Thanks
>|||On Oct 5, 4:02 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> Use Jump to URL instead of jump to report. You have full control over the
> URL which includes collapsing or not the parameter area. Read up on URL
> integration on Books Online. One option for this is that you can if you want
> open up a new window. Then they can just shut down the window when they are
> done. Some examples for you of Jump to URL
> Jump to URL gives you more control than jump to report.
> For the first two examples be careful with the single and double quotes.
> Here is an example of a Jump to URL link I use. This causes Excel to come up
> with the data in a separate window:
> ="javascript:void(window.open('" & Globals!ReportServerUrl &
> "?/SomeFolder/SomeReport&ParamName=" & Parameters!ParamName.Value &
> "&rs:Format=Excel','_blank'))"
> This comes up as html (default format) in a separate window
> ="javascript:void(window.open('" & Globals!ReportServerUrl &
> "?/SomeFolder/SomeReport&ParamName=" &
> Parameters!ParamName.Value','_blank'))"
> If you don't want to have it appear in a new window then do this in jump to
> URL:
> =Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
> Parameters!ParamName.Value
> As far as not using the IE back button? Not sure why that is a requirement.
> Pretty much everyone know how to do that and if they don't you would have to
> train them for an alternative method so train them about the back button.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <trevor.h...@.engenoil.com> wrote in message
> news:1191587402.088348.21130@.r29g2000hsg.googlegroups.com...
>
> > Hi
> > I am using a jump through report action to call a sub report. The main
> > report has the paramters displayed but for the sub report the section
> > where the parameters are displayed is collapsed. Is there a way to
> > change this behaviour for the second report, my users will want to
> > know where the parameters are.
> > A second question, how to you go back to the first report without
> > coding another jump to report action. In the development environment
> > (visual studio) there is a nice blue button that you can use to go
> > back. Once again my users will not want to use the back button on
> > internet explorer.
> > I am using SQL 2005 RS with service pack 2 and am displaying the
> > reports via report viewer control.
> > Thanks- Hide quoted text -
> - Show quoted text -
Thanks Bruce. I am aware of using Jump to URL as a solution and also
of using the back button and I will most probably have to resort to
these "plan b" options. I am really trying to get Reporting Services
to fly in my organisation but I battle to understand why seemingly
little things like the above cant be resolved in future service packs
or releases, i.e.:
1. If Jump to URL is the only way of handling parameter passing
between reports, why is there a Jump to Report action at all. In my
case I am trying to create a dashboard type solution where there are 4
reports involved with each parent report passing parameter values
(combinations of its parameters and field values) down to the child
report.
2. Why is there a nice blue back button in the design environment and
not in the web environment. Yes, my users can use the back button but
we also do other web development where using the back button is
discouraged because it causes post back problems.
If you have any clout, maybe you could suggest some "enhancements" to
an already great product.|||Back up a little. Your first posting was a complaint about not showing the
parameters section. NOT that you had a problem passing parameters. Jump to
Report definitely allows passing parameters. It would be useless if it did
not. When you select jump to report and pick the report to jump to RS
provides a screen for mapping the parameters to whatever you want. Go back
and look for that. Are you having trouble with this?
So, you can use jump to report and take the default behaviour of how RS
shows the report. Or you can use Jump to URL and have full control of how it
shows the report. Either method can easily map parameters.
As far as the development environment being different, well, it is the
development environment and it is not IE.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<trevor.howe@.engenoil.com> wrote in message
news:1191820071.879175.230190@.g4g2000hsf.googlegroups.com...
Snip
> Thanks Bruce. I am aware of using Jump to URL as a solution and also
> of using the back button and I will most probably have to resort to
> these "plan b" options. I am really trying to get Reporting Services
> to fly in my organisation but I battle to understand why seemingly
> little things like the above cant be resolved in future service packs
> or releases, i.e.:
> 1. If Jump to URL is the only way of handling parameter passing
> between reports, why is there a Jump to Report action at all. In my
> case I am trying to create a dashboard type solution where there are 4
> reports involved with each parent report passing parameter values
> (combinations of its parameters and field values) down to the child
> report.
> 2. Why is there a nice blue back button in the design environment and
> not in the web environment. Yes, my users can use the back button but
> we also do other web development where using the back button is
> discouraged because it causes post back problems.
> If you have any clout, maybe you could suggest some "enhancements" to
> an already great product.
>|||On Oct 8, 2:25 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
wrote:
> Back up a little. Your first posting was a complaint about not showing the
> parameters section. NOT that you had a problem passing parameters. Jump to
> Report definitely allows passing parameters. It would be useless if it did
> not. When you select jump to report and pick the report to jump to RS
> provides a screen for mapping the parameters to whatever you want. Go back
> and look for that. Are you having trouble with this?
> So, you can use jump to report and take the default behaviour of how RS
> shows the report. Or you can use Jump to URL and have full control of how it
> shows the report. Either method can easily map parameters.
> As far as the development environment being different, well, it is the
> development environment and it is not IE.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> <trevor.h...@.engenoil.com> wrote in message
> news:1191820071.879175.230190@.g4g2000hsf.googlegroups.com...
> Snip
>
>
> > Thanks Bruce. I am aware of using Jump to URL as a solution and also
> > of using the back button and I will most probably have to resort to
> > these "plan b" options. I am really trying to get Reporting Services
> > to fly in my organisation but I battle to understand why seemingly
> > little things like the above cant be resolved in future service packs
> > or releases, i.e.:
> > 1. If Jump to URL is the only way of handling parameter passing
> > between reports, why is there a Jump to Report action at all. In my
> > case I am trying to create a dashboard type solution where there are 4
> > reports involved with each parent report passing parameter values
> > (combinations of its parameters and field values) down to the child
> > report.
> > 2. Why is there a nice blue back button in the design environment and
> > not in the web environment. Yes, my users can use the back button but
> > we also do other web development where using the back button is
> > discouraged because it causes post back problems.
> > If you have any clout, maybe you could suggest some "enhancements" to
> > an already great product.- Hide quoted text -
> - Show quoted text -
Ok, lets go back to the original mail. I am aware that parameters can
work with Jump to Report and Jump to Url. I have 4 reports with report
1 calling report 2, report 2 calling report 3 and report 3 calling
report 4. Report 1 shows the parameter selection criteria - beautiful.
When I click on a hyperlink within report 1 that calls the jump to
report action for report2, the parameter selection screen in Report 2
is hidden. It gets even worse for report 4 which contains about 4
different parameters. Yes, I could use jump to url but I prefer the
jump to report action (you dont have to doctor the string value to
cater for spaces, etc).
On the back button issue, remember SQL 2000 Reporting services did not
have a nice print feature and we had to rely on the clunky way that
printig in IE. Well enough people complained about it and now there is
a nice print control on the toolbar. What could be so difficult about
putting a back button on the toolbar that navigates back to the parent
report,
Forgive my gripes but I can see by your title that you might just be
able to remove these kind of frustrations in future releases of RS.
Heres hoping..|||Sorry, I thought you wanted to know how to show the parameter section. I
didn't realize you just wanted to complain.
Sum total of your complaint. You don't like using jump to URL even though it
does what you want. You don't like the users using the Internet explorer
back button even though that is a standard way to go backward to another web
page.
If you want to complain fine do so, don't write your posting like you want
help and then get snarky with me.
Also, complaining here is pretty much useless. Very few MS people hang out
here. Here is an official link for complaints/suggestions:
http://connect.microsoft.com/
Bruce Loehle-Conger
MVP SQL Server Reporting Services
<trevor.howe@.engenoil.com> wrote in message
news:1192007368.106861.284440@.d55g2000hsg.googlegroups.com...
> On Oct 8, 2:25 pm, "Bruce L-C [MVP]" <bruce_lcNOS...@.hotmail.com>
> wrote:
>> Back up a little. Your first posting was a complaint about not showing
>> the
>> parameters section. NOT that you had a problem passing parameters. Jump
>> to
>> Report definitely allows passing parameters. It would be useless if it
>> did
>> not. When you select jump to report and pick the report to jump to RS
>> provides a screen for mapping the parameters to whatever you want. Go
>> back
>> and look for that. Are you having trouble with this?
>> So, you can use jump to report and take the default behaviour of how RS
>> shows the report. Or you can use Jump to URL and have full control of how
>> it
>> shows the report. Either method can easily map parameters.
>> As far as the development environment being different, well, it is the
>> development environment and it is not IE.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> <trevor.h...@.engenoil.com> wrote in message
>> news:1191820071.879175.230190@.g4g2000hsf.googlegroups.com...
>> Snip
>>
>>
>> > Thanks Bruce. I am aware of using Jump to URL as a solution and also
>> > of using the back button and I will most probably have to resort to
>> > these "plan b" options. I am really trying to get Reporting Services
>> > to fly in my organisation but I battle to understand why seemingly
>> > little things like the above cant be resolved in future service packs
>> > or releases, i.e.:
>> > 1. If Jump to URL is the only way of handling parameter passing
>> > between reports, why is there a Jump to Report action at all. In my
>> > case I am trying to create a dashboard type solution where there are 4
>> > reports involved with each parent report passing parameter values
>> > (combinations of its parameters and field values) down to the child
>> > report.
>> > 2. Why is there a nice blue back button in the design environment and
>> > not in the web environment. Yes, my users can use the back button but
>> > we also do other web development where using the back button is
>> > discouraged because it causes post back problems.
>> > If you have any clout, maybe you could suggest some "enhancements" to
>> > an already great product.- Hide quoted text -
>> - Show quoted text -
> Ok, lets go back to the original mail. I am aware that parameters can
> work with Jump to Report and Jump to Url. I have 4 reports with report
> 1 calling report 2, report 2 calling report 3 and report 3 calling
> report 4. Report 1 shows the parameter selection criteria - beautiful.
> When I click on a hyperlink within report 1 that calls the jump to
> report action for report2, the parameter selection screen in Report 2
> is hidden. It gets even worse for report 4 which contains about 4
> different parameters. Yes, I could use jump to url but I prefer the
> jump to report action (you dont have to doctor the string value to
> cater for spaces, etc).
> On the back button issue, remember SQL 2000 Reporting services did not
> have a nice print feature and we had to rely on the clunky way that
> printig in IE. Well enough people complained about it and now there is
> a nice print control on the toolbar. What could be so difficult about
> putting a back button on the toolbar that navigates back to the parent
> report,
> Forgive my gripes but I can see by your title that you might just be
> able to remove these kind of frustrations in future releases of RS.
> Heres hoping..
>