Showing posts with label parameters. Show all posts
Showing posts with label parameters. Show all posts

Friday, March 30, 2012

jumping to a report

I have a wierd problem here.
I am using jump to a report feature and passed 2 parameters to the report.
It works fine in the review but when i see that in the webpage (i did using
reportviewer) it does not show the report and gets to the first page of the
report.
Please help me outNow I'm the report developer, not the coder, so my explanation may not
be the most detailed. It's a page post back issue. I'm assuming your
using aspx, and refreshing the page every time your report changes.
You need to include an 'ispostback = false' so the entire page doesn't
post back, just the report. It solved our issues. Hope this helps
Smith

Jump to URL - New Window - Ampersand

I have a Jump to URL hyperlink action using the "javascript:
void(window.open)" code. This works great, except when one of the parameters
contains an ampersand. I get an error saying that the "path of the item is
not valid. The full path must be less than 260 characters long, muster start
with slash..."
One of my parameters for the report that first comes up is
"OfficeDescription" which may contain an ampersand ("Boise R&D"). I'm
passing this to the URL as listed below. It only fails if there is that
ampersand in the OfficeDescription ("Boise Sales" works fine). I'm tried
replacing the "&" with %26 but I can't get that to work.
This works fine if I use a "Jump to Report" and pass the parameters that
way, but I need to pop up the report in a new window.
="javascript:void(window.open('"&Globals!ReportServerUrl+ "?" &
Globals!ReportFolder & "/Producer Detail&OfficeDescription=" &
Parameters!OfficeDescription.Value & "&Producer=" & Fields!Producer.Value &
"&rc%3aParameters=false','_blank','height=530px,left=1px,location=no,menubar=no,resizable=yes,scrollbars=yes,toolbar=no,top=1px,width=780px'))"
Thanks for any advice anyone cares to offer!Parameter values must be URLEncoded. Please perform the following steps:
* load the report in report designer
* go to the report menu -> report properties -> References tab
* in the "References:" list, add a reference to System.Web, and click OK
* in the report, modify your expression to use the HttpUtility.UrlEncode
function (see MSDN:
http://msdn2.microsoft.com/en-us/library/system.web.httputility.urlencode):
="javascript:void(window.open('"&Globals!ReportServerUrl+ "?" &
Globals!ReportFolder & "/Producer Detail&OfficeDescription=" &
System.Web.HttpUtility.UrlEncode(Parameters!OfficeDescription.Value) &
"&Producer=" & System.Web.HttpUtility.UrlEncode(Fields!Producer.Value) &
"&rc%3aParameters=false','_blank','height=530px,left=1px,location=no,menubar=no,resizable=yes,scrollbars=yes,toolbar=no,top=1px,width=780px'))"
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"kaibh" <kaibh@.discussions.microsoft.com> wrote in message
news:7EAE0CF0-2C9C-47A8-8A2D-B5861AFA5740@.microsoft.com...
>I have a Jump to URL hyperlink action using the "javascript:
> void(window.open)" code. This works great, except when one of the
> parameters
> contains an ampersand. I get an error saying that the "path of the item
> is
> not valid. The full path must be less than 260 characters long, muster
> start
> with slash..."
> One of my parameters for the report that first comes up is
> "OfficeDescription" which may contain an ampersand ("Boise R&D"). I'm
> passing this to the URL as listed below. It only fails if there is that
> ampersand in the OfficeDescription ("Boise Sales" works fine). I'm tried
> replacing the "&" with %26 but I can't get that to work.
> This works fine if I use a "Jump to Report" and pass the parameters that
> way, but I need to pop up the report in a new window.
> ="javascript:void(window.open('"&Globals!ReportServerUrl+ "?" &
> Globals!ReportFolder & "/Producer Detail&OfficeDescription=" &
> Parameters!OfficeDescription.Value & "&Producer=" & Fields!Producer.Value
> &
> "&rc%3aParameters=false','_blank','height=530px,left=1px,location=no,menubar=no,resizable=yes,scrollbars=yes,toolbar=no,top=1px,width=780px'))"
> Thanks for any advice anyone cares to offer!
>|||Robert, thanks for the feedback, however I'm still getting the same error:
Reporting Services Error
The path of the item '/OnDemand/Producer Detail,C' is not valid.The full
path must be less than 260 characters long, must start with slash; other
restrictions apply. Check the documentation for complete set of restrictions.
(rsInvalidItemPath)
The HTML generated for this link looks like:
<a style="text-decoration:none;color:Black"
href="javascript:void(window.open('https://my.reportserver.com/ReportServer?/OnDemand/Producer%20Detail&OfficeDescription=Boise+r%26D&Producer=JSL&rc%3aParameters=false','_blank','height=530px,left=1px,location=no,menubar=no,resizable=yes,scrollbars=yes,toolbar=no,top=1px,width=780px'))" TARGET="_top">JSL</a>
The "Boise R&D" is getting encoded as "Boise+R%26D", so that's good right?
But since I'm still getting this error, I assume there must be something else
that I'm missing.
Thanks
"Robert Bruckner [MSFT]" wrote:
> Parameter values must be URLEncoded. Please perform the following steps:
> * load the report in report designer
> * go to the report menu -> report properties -> References tab
> * in the "References:" list, add a reference to System.Web, and click OK
> * in the report, modify your expression to use the HttpUtility.UrlEncode
> function (see MSDN:
> http://msdn2.microsoft.com/en-us/library/system.web.httputility.urlencode):
> ="javascript:void(window.open('"&Globals!ReportServerUrl+ "?" &
> Globals!ReportFolder & "/Producer Detail&OfficeDescription=" &
> System.Web.HttpUtility.UrlEncode(Parameters!OfficeDescription.Value) &
> "&Producer=" & System.Web.HttpUtility.UrlEncode(Fields!Producer.Value) &
> "&rc%3aParameters=false','_blank','height=530px,left=1px,location=no,menubar=no,resizable=yes,scrollbars=yes,toolbar=no,top=1px,width=780px'))"
> -- Robert
> This posting is provided "AS IS" with no warranties, and confers no rights.|||I also am trying to do this. It works great in the IDE, but I get the
following error when publishing the report to Report Manager on my local
machine and any servers.
Request for the permission of type System.Web.AspNetHostingPermission,
System, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
failed.
It is probably permissions. How would I modify rssrvpolicy.config to allow
the execution of System.Web assembly?
Dan Bock
"kaibh" wrote:
> Robert, thanks for the feedback, however I'm still getting the same error:
> Reporting Services Error
> The path of the item '/OnDemand/Producer Detail,C' is not valid.The full
> path must be less than 260 characters long, must start with slash; other
> restrictions apply. Check the documentation for complete set of restrictions.
> (rsInvalidItemPath)
> The HTML generated for this link looks like:
> <a style="text-decoration:none;color:Black"
> href="http://links.10026.com/?link=javascript:void(window.open('https://my.reportserver.com/ReportServer?/OnDemand/Producer%20Detail&OfficeDescription=Boise+r%26D&Producer=JSL&rc%3aParameters=false','_blank','height=530px,left=1px,location=no,menubar=no,resizable=yes,scrollbars=yes,toolbar=no,top=1px,width=780px'))" TARGET="_top">JSL</a>
> The "Boise R&D" is getting encoded as "Boise+R%26D", so that's good right?
> But since I'm still getting this error, I assume there must be something else
> that I'm missing.
> Thanks
>
> "Robert Bruckner [MSFT]" wrote:
> > Parameter values must be URLEncoded. Please perform the following steps:
> > * load the report in report designer
> > * go to the report menu -> report properties -> References tab
> > * in the "References:" list, add a reference to System.Web, and click OK
> > * in the report, modify your expression to use the HttpUtility.UrlEncode
> > function (see MSDN:
> > http://msdn2.microsoft.com/en-us/library/system.web.httputility.urlencode):
> > ="javascript:void(window.open('"&Globals!ReportServerUrl+ "?" &
> > Globals!ReportFolder & "/Producer Detail&OfficeDescription=" &
> > System.Web.HttpUtility.UrlEncode(Parameters!OfficeDescription.Value) &
> > "&Producer=" & System.Web.HttpUtility.UrlEncode(Fields!Producer.Value) &
> > "&rc%3aParameters=false','_blank','height=530px,left=1px,location=no,menubar=no,resizable=yes,scrollbars=yes,toolbar=no,top=1px,width=780px'))"
> >
> > -- Robert
> > This posting is provided "AS IS" with no warranties, and confers no rights.
>

Wednesday, March 28, 2012

Jump to report, Parameters visible

I have an action in my report: jump to report. It works great!
However - I don't want to collapse the parameters... when I jump.
How do I achieve that?
I know with SP1, the parameters are collapsed, but available. I want
to 'uncollapse' them.
ThanksYou need to use the URL Access instead (at least that is the only way I
found to do it). Note that you can use some of the global variables with the
expression builder to create this on the fly (so it changes with wherever it
is deployed.
http://servername/Reports/Pages/Report.aspx?ServerUrl=http://servername/ReportServer%3f/directoryname%252fReportName&Parameter1=blahblah&rc:Parameters=True
Bruce L-C
"Harsh" <creative@.mailcity.com> wrote in message
news:fa671a26.0407141011.7b716b31@.posting.google.com...
> I have an action in my report: jump to report. It works great!
> However - I don't want to collapse the parameters... when I jump.
> How do I achieve that?
> I know with SP1, the parameters are collapsed, but available. I want
> to 'uncollapse' them.
> Thanks

Jump to Report Without Parameters

Hi,

Is there any way in Rs2000 "Jump to Report" Action, to pass only some off the target report parameters, and when the report opens fill the rest from the target report parameter area?

I can make this work in VS2003 but not in Report Manager.

In Report Manager when you click the link it just clear the screen and stays like that.

Thank you for your help

Rgranada

i do have a crude way of doing it and i still looking out for the best way to do it.

for example, lets take @.Empno is the parameter and u want to make it optional

so declare another variable like @.ES

when u r passing employee number , then pass @.ES = 'S' ( means selected)

when u do not want to use @.EmpNO , then pass @.ES = 'A' (means all)

use in ur query

where (@.EmpNo = '123' and @.ES = 'S') or (@.EmpNo like '%' and @.ES = 'A')

hope this works for u

Jump to Report Parameters not passing correctly defualt values use

I have a Report with a chart on it and have a Jump to report setup on the
Action tab of the Chart control. I pass the report Parameters in the Jump to
Report. My problem is that if I have defualt values for the report
parameters, when I pass values in the Jump to report they get over written by
the defualt values. If I remove
the Defualt values my report parameters get passed correctly with the Jump
to report. Do defualt values over ride report Parameters that are passed in
the jump to report command? Can I make it so that defualt values will only
get used if I do not pass in a value to the report?
MikeIf you dont provide any value during drill-through then only it will take the
default values. If you provide some value then it will take that value. Check
if you are passing all the parameter to the Dill-Through report. If any
parameter is missing then the drill-throught report will take the default
value provided . This defult value is of the drill-through defaul value not
the parent report default value.
"Hotwheels" wrote:
> I have a Report with a chart on it and have a Jump to report setup on the
> Action tab of the Chart control. I pass the report Parameters in the Jump to
> Report. My problem is that if I have defualt values for the report
> parameters, when I pass values in the Jump to report they get over written by
> the defualt values. If I remove
> the Defualt values my report parameters get passed correctly with the Jump
> to report. Do defualt values over ride report Parameters that are passed in
> the jump to report command? Can I make it so that defualt values will only
> get used if I do not pass in a value to the report?
> Mike|||If I am passing a report parameter it does not seem to work like you say and
I have to remove the defualt value to get it to work.
If I pass the Field value of the chart it works like you say.
I tried this with a report with one Report parameter to make it easy.
Why would passing a report Parameter cause a problem?
"Bava Mani" wrote:
> If you dont provide any value during drill-through then only it will take the
> default values. If you provide some value then it will take that value. Check
> if you are passing all the parameter to the Dill-Through report. If any
> parameter is missing then the drill-throught report will take the default
> value provided . This defult value is of the drill-through defaul value not
> the parent report default value.
> "Hotwheels" wrote:
> > I have a Report with a chart on it and have a Jump to report setup on the
> > Action tab of the Chart control. I pass the report Parameters in the Jump to
> > Report. My problem is that if I have defualt values for the report
> > parameters, when I pass values in the Jump to report they get over written by
> > the defualt values. If I remove
> > the Defualt values my report parameters get passed correctly with the Jump
> > to report. Do defualt values over ride report Parameters that are passed in
> > the jump to report command? Can I make it so that defualt values will only
> > get used if I do not pass in a value to the report?
> >
> > Mike

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..
>

Jump to report length error

I have a detailed report that needs a lot of inputs, and when I use a
first report and use "jump to report" to pass in parameters, the URL is
too long and IE does not open it.
Any ideas?Hi,
URL should not be more than 2048 bytes. So just use MS word to
measure no of characters. If characters are less than 2K then I am sure
that you are not passing all the parameters that details report is
expecting.
Cheers,
Mahesh

Jump to Report Issue

I have a "Jump to Report" issue. I have created a report that runs itself
with new parameters when a cell is clicked on. It works great except that
when it is run on the web, the "Jump to Report" has no access to the
parameters. I need to be able to have the parameters visible so the users
can change out their values at will.
I can not find any settings to turn on or off the parameters in the Jump-to
screens.You have to use Jump to URL. Here is an example of an expression that I use
for this. Note the global variable that puts in the server name of where the
report is running from.
=Globals!ReportServerUrl & "?/Inventory/Similar Loads&Manifest=" &
First(Fields!manifstdocno.Value, "LoadID") &"&WasteIDNum=" &
First(Fields!wasteidnum.Value, "LoadID")
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"mlapoint" <mlapoint@.discussions.microsoft.com> wrote in message
news:F9EDC25A-F1E3-48A5-9359-D6C4DEF27D4F@.microsoft.com...
> I have a "Jump to Report" issue. I have created a report that runs itself
> with new parameters when a cell is clicked on. It works great except that
> when it is run on the web, the "Jump to Report" has no access to the
> parameters. I need to be able to have the parameters visible so the users
> can change out their values at will.
> I can not find any settings to turn on or off the parameters in the
Jump-to
> screens.

Jump to report and parameters

I have a table where I want to jump to a different report based on the value
in the table cell. The report that I am jumping to has a parameter, and the
parameter value that I need to pass is based on the table cell's value. I
know how to set this up in the report but can't figure out how filter the
dataset that has my parameter values, and I can't filter the dataset using
ReportItems.
If I were to write some pseudocode using SQL it would look something like
this:
PopupReport(Select Param From ParamTable Where ParamKey = Fields!MyTextBox.Value)
Thanks...
Regards,
SteveIf the report you are jumping to has parameters then I am confused on the
issue. When setting up the jump to report you set the parameters of the
report you are jumping to, in this case to the field. That being the case,
what is the problem? The report you are jumping to must be able to accept
the parameter and return the correct data.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Steve" <MyNoSpam@.NoSpam.org> wrote in message
news:00B417ED-8954-4CAC-A07B-48FD361A3575@.microsoft.com...
>I have a table where I want to jump to a different report based on the
>value
> in the table cell. The report that I am jumping to has a parameter, and
> the
> parameter value that I need to pass is based on the table cell's value. I
> know how to set this up in the report but can't figure out how filter the
> dataset that has my parameter values, and I can't filter the dataset using
> ReportItems.
> If I were to write some pseudocode using SQL it would look something like
> this:
> PopupReport(Select Param From ParamTable Where ParamKey => Fields!MyTextBox.Value)
> Thanks...
> Regards,
> Steve|||Hi Bruce,
The problem I have is that the parameter value that I need to pass is in a
SQL table and I need to select the correct parameter based on the cell I am
clicking on.
For instance, the textbox value I am clicking on contains a sales region,
e.g. Central, Northeast, etc, and I want to pass a list of the salereps for
that region into another report. The list of salesreps for that region is
contained in a separate sql table and the sql to find the appropriate list of
salesreps would be something like "Select RepList From Configs Where Region ='Central'", except that the region varies with the row I am clicking on in
the Reporting Services table.
I can make this work if I do something like this for the parameter
expression in the report:
iif(Fields!Region.Value="Central","1,2,3",iif(Fields!Region.Value="Northeast","4,5,6",....))
, but it's kind of ugly and hardcoded...
Hope this is clearer and thanks for your response.
Regards,
Steve
"Bruce L-C [MVP]" wrote:
> If the report you are jumping to has parameters then I am confused on the
> issue. When setting up the jump to report you set the parameters of the
> report you are jumping to, in this case to the field. That being the case,
> what is the problem? The report you are jumping to must be able to accept
> the parameter and return the correct data.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Steve" <MyNoSpam@.NoSpam.org> wrote in message
> news:00B417ED-8954-4CAC-A07B-48FD361A3575@.microsoft.com...
> >I have a table where I want to jump to a different report based on the
> >value
> > in the table cell. The report that I am jumping to has a parameter, and
> > the
> > parameter value that I need to pass is based on the table cell's value. I
> > know how to set this up in the report but can't figure out how filter the
> > dataset that has my parameter values, and I can't filter the dataset using
> > ReportItems.
> >
> > If I were to write some pseudocode using SQL it would look something like
> > this:
> >
> > PopupReport(Select Param From ParamTable Where ParamKey => > Fields!MyTextBox.Value)
> >
> > Thanks...
> >
> > Regards,
> > Steve
>
>

Jump to report and also URL based on parameters values

Hi,
i am doing a page whereby user can navigate to other report by clicking on
the respective column data and i am now using this navigating expression:
=Switch(Fields!Status.Value = "Pending", "EvaluatePending",
Fields!Status.Value = "Rejected", "ViewRejected", Fields!Status.Value = "Accepted", "ViewAccepted")
This expression only allows me to jump to other report but not to a URL
because i try using the following statement but got an error:
=Switch(Fields!Status.Value = "Pending",
"="http://localhost/SSS-ASP/EvaluatePending.aspx?SuggestionID=" &
Fields!SuggestionID.Value", Fields!Status.Value = "Rejected", "ViewRejected",
Fields!Status.Value = "Accepted", "ViewAccepted")
For the above statement what i want to achieved was that when user click on
the column with the Status=Pending, it will go to the
URL="http://localhost/SSS-ASP/EvaluatePending.aspx?SuggestionID=" &
Fields!SuggestionID.Value. If Status=Rejected, it will jump to the report
ViewRejected and lastly if Status=Accepted, it will jump to the report
ViewAccepted. Hope somebody can guide me with the correct expression.
Thanks in advance. =)Hello, is anybody able to help me with this problem? really need help with
this still not sure how to solve. Thanks
"JiaN" wrote:
> Hi,
> i am doing a page whereby user can navigate to other report by clicking on
> the respective column data and i am now using this navigating expression:
> =Switch(Fields!Status.Value = "Pending", "EvaluatePending",
> Fields!Status.Value = "Rejected", "ViewRejected", Fields!Status.Value => "Accepted", "ViewAccepted")
> This expression only allows me to jump to other report but not to a URL
> because i try using the following statement but got an error:
> =Switch(Fields!Status.Value = "Pending",
> "="http://localhost/SSS-ASP/EvaluatePending.aspx?SuggestionID=" &
> Fields!SuggestionID.Value", Fields!Status.Value = "Rejected", "ViewRejected",
> Fields!Status.Value = "Accepted", "ViewAccepted")
> For the above statement what i want to achieved was that when user click on
> the column with the Status=Pending, it will go to the
> URL="http://localhost/SSS-ASP/EvaluatePending.aspx?SuggestionID=" &
> Fields!SuggestionID.Value. If Status=Rejected, it will jump to the report
> ViewRejected and lastly if Status=Accepted, it will jump to the report
> ViewAccepted. Hope somebody can guide me with the correct expression.
> Thanks in advance. =)

Jump to Report & Multi Value vs. Single Value

I have a parameterized main report that contains a link to a sub report with parameters. Then from the sub report I have a link that takes you back to main report. If I use multi value parameters or single value parameters the links going back and forth between the two reports works just dandy, when I run it on my PC. However when I deploy the reports to the Web Server, the link going from the sub report back to the main report only works if the parameters are single select. Going from the Main to the Sub it doesn’t matter.

This is the error I get using multi select parameters going from the sub report back to the main.

The path of the item "(null)" is not valid. The path must be less than 260 characters long and must start with slash. Other restrictions apply. (rsInvalidItemPath)

Any suggestions?

By any chance, are the drillthrough links located in the page header or page footer?

-- Robert

Jump to report

Hi

I want to use Jump to Report option under Navigation tab.

I have two reports both with Same parameters and parameters are multiple value selectable.

In Jump to Report this is how I set the parameter value.

LeadershipTeamId =Join(Parameters!LeadershipTeamId.Value,", ")

CostCentreId =Join(Parameters!CostCentreId.Value,", ")

CostElementGroupId =Fields!CostElementGroupId.Value

This works fine if I have only one value selected for CostCentre and LeadershipTeam but when I select the multiple value I get the following error.

  • The value provided for the report parameter 'LeadershipTeamId' is not valid for its type. (rsReportParameterTypeMismatch)

    Am I missing anything here?

    Any help would be highly appreciated.

    Best Regards

    I used this expression and it seems to be working.

    =Split(Join(Parameters!LeadershipTeamId.Value,", "),",")

    Correct me if this is not the right approach.

    Now my problem is When I jump to second report the CostCentre Parameter value is not set.

    Because, costcentre value is depend on the LeadershipTeam value.

    So when I jump to second report I have LeadershipTeam value set but I have to select costcentre value.

    Is it possible to make CostCentre selected when someone jump to the report?

    Thanks for your help

    Regards

    Update: By the way it works if I select only one CostCentre.

    |||

    Solved it using this thread.

    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=163803&SiteID=1

    Thanks guys

    Amit

  • Monday, March 26, 2012

    Juggling Parameters

    I am reporting off a star-schema data warehouse. I have three datasets that I
    use to populate parameters, and one master dataset that uses the values from
    all three to populate the report. The way I have set up the master dataset
    is:
    SELECT *
    FROM t_policy_info
    WHERE month_key = @.month_key AND
    paper_desc = @.paper_desc AND
    unit_desc = @.unit_desc
    Matching on non-key values is very time-consuming. For the @.paper_desc and
    @.unit_desc datasets, I'm only pulling back the descriptions so that they
    appear in the dropdowns at the top of the report.
    How should I configure the datasets so that the master query matches
    WHERE month_key = @.month_key AND
    paper_key= @.paper_key AND
    unit_key = @.unit_key ?
    Should the paper and unit datasets also contain the key fields so that they
    can be matched in the master dataset? How do I prevent the user from being
    prompted for the keys (which they shouldn't)?
    This is really a performance issue, and while I could make it work with
    straight SQL, I'm not sure how to implement it with Reporting Services.
    Thanks,
    MikeHave you looked at the parametere Label Field/ Value Field inputs , one of
    them is what is displayed to the user and other is what is passed to the
    query.?
    When you create your query for the main dataset along with the month also
    pass the paper_key and unit_key parameters, as input by the user.
    HTH
    "Bassist695" <Bassist695@.discussions.microsoft.com> wrote in message
    news:8549E9F8-0F83-40A6-9737-864C4C302045@.microsoft.com...
    >I am reporting off a star-schema data warehouse. I have three datasets that
    >I
    > use to populate parameters, and one master dataset that uses the values
    > from
    > all three to populate the report. The way I have set up the master dataset
    > is:
    > SELECT *
    > FROM t_policy_info
    > WHERE month_key = @.month_key AND
    > paper_desc = @.paper_desc AND
    > unit_desc = @.unit_desc
    > Matching on non-key values is very time-consuming. For the @.paper_desc and
    > @.unit_desc datasets, I'm only pulling back the descriptions so that they
    > appear in the dropdowns at the top of the report.
    > How should I configure the datasets so that the master query matches
    > WHERE month_key = @.month_key AND
    > paper_key= @.paper_key AND
    > unit_key = @.unit_key ?
    > Should the paper and unit datasets also contain the key fields so that
    > they
    > can be matched in the master dataset? How do I prevent the user from being
    > prompted for the keys (which they shouldn't)?
    > This is really a performance issue, and while I could make it work with
    > straight SQL, I'm not sure how to implement it with Reporting Services.
    > Thanks,
    > Mike

    Monday, March 19, 2012

    Joining table UDFs in queries

    Hi,
    I've got a table UDF which takes two parameters and returns a table, as
    follows:
    CREATE FUNCTION dbo.ftblPeriodYear (@.pCompanyID varchar(15), @.pDate
    datetime)
    RETURNS @.tblPeriodYear TABLE
    (
    Period tinyint,
    Year smallint
    )
    AS
    BEGIN
    <snipped to save space>
    RETURN
    END
    That works fine. However, is it possible to use this UDF as part of a query
    where the input parameters come from another table?
    E.g. the two input parameters I want to pass to the function are contained
    within the Sales table, and I could output them as follows:
    SELECT
    CompanyID,
    SaleDate,
    <other fields>
    FROM
    Sales
    Ideally, I'm looking for some way of combining the query on the table with
    the UDF e.g.
    SELECT
    CompanyID,
    SaleDate,
    ftblPeriodYear(CompanyID, SaleDate)
    FROM
    Sales
    Is this even possible?
    Any assistance gratefully received.
    MarkI'm afraid not in SQL Server 2000. This is new functionality added in SQL
    Server 2005 via the APPLY table operator, e.g.,
    SELECT ...
    FROM Sales AS S
    CROSS APPLY ftblPeriodYear(S.CompanyID, S.SaleDate) AS F;
    You can find more details here:
    http://www.windowsitpro.com/Article...47145.html?Ad=1
    http://msdn.microsoft.com/library/d...TSQLEnhance.asp
    BG, SQL Server MVP
    www.SolidQualityLearning.com
    Join us for the SQL Server 2005 launch at the SQL W in Israel!
    [url]http://www.microsoft.com/israel/sql/sqlw/default.mspx[/url]
    "Mark Rae" <mark@.mark-N-O-S-P-A-M-rae.co.uk> wrote in message
    news:eueZ2kxyFHA.460@.TK2MSFTNGP15.phx.gbl...
    > Hi,
    > I've got a table UDF which takes two parameters and returns a table, as
    > follows:
    > CREATE FUNCTION dbo.ftblPeriodYear (@.pCompanyID varchar(15), @.pDate
    > datetime)
    > RETURNS @.tblPeriodYear TABLE
    > (
    > Period tinyint,
    > Year smallint
    > )
    > AS
    > BEGIN
    > <snipped to save space>
    > RETURN
    > END
    > That works fine. However, is it possible to use this UDF as part of a
    > query where the input parameters come from another table?
    > E.g. the two input parameters I want to pass to the function are contained
    > within the Sales table, and I could output them as follows:
    > SELECT
    > CompanyID,
    > SaleDate,
    > <other fields>
    > FROM
    > Sales
    > Ideally, I'm looking for some way of combining the query on the table with
    > the UDF e.g.
    > SELECT
    > CompanyID,
    > SaleDate,
    > ftblPeriodYear(CompanyID, SaleDate)
    > FROM
    > Sales
    >
    > Is this even possible?
    > Any assistance gratefully received.
    > Mark
    >|||That :
    SELECT
    CompanyID,
    SaleDate,
    ftblPeriodYear(CompanyID, SaleDate)
    FROM=20
    Sales=20
    doesn=B4t work. :-(|||"Jens" <Jens@.sqlserver2005.de> wrote in message
    news:1128675411.933739.210250@.g14g2000cwa.googlegroups.com...

    >That :
    >SELECT
    > CompanyID,
    > SaleDate,
    > ftblPeriodYear(CompanyID, SaleDate)
    >FROM
    > Sales
    >
    >doesnt work. :-(
    Er, yeah I know - that was the reason for my post...|||"Itzik Ben-Gan" <itzik@.REMOVETHIS.SolidQualityLearning.com> wrote in message
    news:unelksxyFHA.3720@.TK2MSFTNGP14.phx.gbl...

    > I'm afraid not in SQL Server 2000. This is new functionality added in SQL
    > Server 2005 via the APPLY table operator, e.g.,
    Thanks - I was vaguely aware that there was something like this in SQL
    Server 2005, but wondered if it had an equivalent in 2000...

    Monday, March 12, 2012

    Joining different datasets with parameters

    Hi all,

    lets say i have one table with colour ids and colour names, and another table with broad-leafed trees and different colour id fields for root, leafs and trunk:

    Table colours:
    integer field colour_id, varchar field colour_name
    Table trees:
    varchar field tree_type, integer field leaf_colour_id,
    integer field trunk_colour_id, integer field root_colour_id

    one way to get the fields would be:

    select T.tree_type, C1.colour_name as leaf_colour_name,
    C2.colour_name as trunk_colour_name, C3.colour_name as root_colour_name
    from trees as T
    inner join colours as C1 on C1.colour_id = leaf_colour_id
    inner join colours as C2 on C2.colour_id = trunk_colour_id
    inner join colours as C3 on C3.colour_id = root_colour_id;

    But i would like to do that with some kind of inline function like:
    colourName := select colour_name from colours where colour_id = @.colourId;
    and then:
    select tree_type, colourName(leaf_colour_id), colourName(trunk_colour_id), colourName(root_colour_id) from trees;

    Is that possible? Any comments welcome.

    Thanks,
    haraldIn Sql Server, you can create a User Defined Function (Scalar) which will produce this. It will make code more readable but will slow it down a bit.
    See the templates in SQL Server, and this article.
    It would be something like:
    CREATE FUNCTION fnGetColourName(@.ColourID as int)
    RETURNS int
    as
    BEGIN
    DECLARE @.Value as int
    SET @.Value = (SELECT MAX(Colour_name)
    FROM Colours
    WHERE colour_id = @.ColourID
    END
    RETURN @.Value
    SELECT dbo.fnGetColourName(leaf_colour_id) as leafColour
    FROM trees
    Alternatively, you can use the Custom Code section of the report to create a function that will do the same thing, see examples from Bryant Likes's blog here.|||

    Hi wavemash,

    thanks for your reply, now my sql statement is more readable

    Thanks,
    harald