Hello. I have javascript in a bunch of my reports so that when jumping to a
url in the action property everything would go to a new browser window.
Everything is working just fine (after I upgraded the service pack so I could
do it) but now all of a sudden it doesn't work on any of the reports. Nothing
has changed on the box and none of the reports have been touched. Everything
else appears to be working as intended.
Any ideas? Any help would be very much appreciated. Thanks!Hi can i know what is the javascript you used? There is a some change in SP1
2005RS that made to do this. Few javascript code added to the RS report
manager has been changed to support and block some feature...
"dcray" wrote:
> Hello. I have javascript in a bunch of my reports so that when jumping to a
> url in the action property everything would go to a new browser window.
> Everything is working just fine (after I upgraded the service pack so I could
> do it) but now all of a sudden it doesn't work on any of the reports. Nothing
> has changed on the box and none of the reports have been touched. Everything
> else appears to be working as intended.
> Any ideas? Any help would be very much appreciated. Thanks!|||Hi, it wasn't until I upgraded the service pack that it would work at all,
and after applied worked fine just as anticipated. Nothing fancy, now all of
reports that use this js are broke and nothing has changed
="javascript:void(window.open('http://www.google.com'))"
I also tried specifiying the target window
="javascript:void(window.open('http://www.google.com','_blank'))"
still not working. These are the things that have been added to the box
reporting services is on since the reports were impliented and working with
the javascript in the action property:
Windows Malicious Software Removal Tool
Security Update for Microsoft Data Access Components 2.7 SP1
Cumulative Security Update for IE 6 SP1
Security Update for Windows 200
Cumulative Security Update for Outlook Express 6 SP1
just in case any of these might cause a prolblem...you never know.
thanks!!
"Bava Mani" wrote:
> Hi can i know what is the javascript you used? There is a some change in SP1
> 2005RS that made to do this. Few javascript code added to the RS report
> manager has been changed to support and block some feature...
> "dcray" wrote:
> > Hello. I have javascript in a bunch of my reports so that when jumping to a
> > url in the action property everything would go to a new browser window.
> > Everything is working just fine (after I upgraded the service pack so I could
> > do it) but now all of a sudden it doesn't work on any of the reports. Nothing
> > has changed on the box and none of the reports have been touched. Everything
> > else appears to be working as intended.
> >
> > Any ideas? Any help would be very much appreciated. Thanks!|||I have a report I designed in RS 2000 and converted to RS 2005. I just tried
it out and it worked fine:
= "javascript:void(window.open('http://www.google.com','_blank'))"
Looks exactly the same as below.
So, might be something else but it is not RS 2005. This requires RS 2000 SP1
or greater. I have all the latest security updates at the server and the
client (Server is 2003 SP1, client XP Pro SP2).
Anyway, not a solution but at least another data point for you.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"dcray" <dcray@.discussions.microsoft.com> wrote in message
news:89F48B08-2279-4D1D-8FE6-FB1B98D431B8@.microsoft.com...
> Hi, it wasn't until I upgraded the service pack that it would work at all,
> and after applied worked fine just as anticipated. Nothing fancy, now all
> of
> reports that use this js are broke and nothing has changed
> ="javascript:void(window.open('http://www.google.com'))"
> I also tried specifiying the target window
> ="javascript:void(window.open('http://www.google.com','_blank'))"
> still not working. These are the things that have been added to the box
> reporting services is on since the reports were impliented and working
> with
> the javascript in the action property:
> Windows Malicious Software Removal Tool
> Security Update for Microsoft Data Access Components 2.7 SP1
> Cumulative Security Update for IE 6 SP1
> Security Update for Windows 200
> Cumulative Security Update for Outlook Express 6 SP1
> just in case any of these might cause a prolblem...you never know.
> thanks!!
>
> "Bava Mani" wrote:
>> Hi can i know what is the javascript you used? There is a some change in
>> SP1
>> 2005RS that made to do this. Few javascript code added to the RS report
>> manager has been changed to support and block some feature...
>> "dcray" wrote:
>> > Hello. I have javascript in a bunch of my reports so that when jumping
>> > to a
>> > url in the action property everything would go to a new browser window.
>> > Everything is working just fine (after I upgraded the service pack so I
>> > could
>> > do it) but now all of a sudden it doesn't work on any of the reports.
>> > Nothing
>> > has changed on the box and none of the reports have been touched.
>> > Everything
>> > else appears to be working as intended.
>> >
>> > Any ideas? Any help would be very much appreciated. Thanks!|||turns out the problem is that some of the urls to the reports that were
getting passed around used an alias for the machine that hasn't been set up
properly as one of the host headers
"Bruce L-C [MVP]" wrote:
> I have a report I designed in RS 2000 and converted to RS 2005. I just tried
> it out and it worked fine:
> = "javascript:void(window.open('http://www.google.com','_blank'))"
> Looks exactly the same as below.
> So, might be something else but it is not RS 2005. This requires RS 2000 SP1
> or greater. I have all the latest security updates at the server and the
> client (Server is 2003 SP1, client XP Pro SP2).
> Anyway, not a solution but at least another data point for you.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "dcray" <dcray@.discussions.microsoft.com> wrote in message
> news:89F48B08-2279-4D1D-8FE6-FB1B98D431B8@.microsoft.com...
> >
> > Hi, it wasn't until I upgraded the service pack that it would work at all,
> > and after applied worked fine just as anticipated. Nothing fancy, now all
> > of
> > reports that use this js are broke and nothing has changed
> >
> > ="javascript:void(window.open('http://www.google.com'))"
> >
> > I also tried specifiying the target window
> >
> > ="javascript:void(window.open('http://www.google.com','_blank'))"
> >
> > still not working. These are the things that have been added to the box
> > reporting services is on since the reports were impliented and working
> > with
> > the javascript in the action property:
> >
> > Windows Malicious Software Removal Tool
> > Security Update for Microsoft Data Access Components 2.7 SP1
> > Cumulative Security Update for IE 6 SP1
> > Security Update for Windows 200
> > Cumulative Security Update for Outlook Express 6 SP1
> >
> > just in case any of these might cause a prolblem...you never know.
> > thanks!!
> >
> >
> >
> > "Bava Mani" wrote:
> >
> >> Hi can i know what is the javascript you used? There is a some change in
> >> SP1
> >> 2005RS that made to do this. Few javascript code added to the RS report
> >> manager has been changed to support and block some feature...
> >>
> >> "dcray" wrote:
> >>
> >> > Hello. I have javascript in a bunch of my reports so that when jumping
> >> > to a
> >> > url in the action property everything would go to a new browser window.
> >> > Everything is working just fine (after I upgraded the service pack so I
> >> > could
> >> > do it) but now all of a sudden it doesn't work on any of the reports.
> >> > Nothing
> >> > has changed on the box and none of the reports have been touched.
> >> > Everything
> >> > else appears to be working as intended.
> >> >
> >> > Any ideas? Any help would be very much appreciated. Thanks!
>
>
Showing posts with label reports. Show all posts
Showing posts with label reports. Show all posts
Friday, March 30, 2012
Jump to URL mangling
I am using "Jump to URL" in a few reports to jump to other reports on the
same reporting services instance. The problem I'm having is that when RS
renders the report, it changes the URL to include a prefix of
"http://reportingserver.domain.com/Reports/Pages/Report.aspx?ServerUrl=".
This is then followed by the actual URL I want to jump to. However, I don't
want this prefix to be applied. It seems to only happen when the
destination of the jump is the reporting server - if I jump to another of
our web servers, the prefix isn't applied.
I am running RS 2000 SP2 on Windows 2000 Advanced Server SP4. Also, the
URLRoot element in RSReportServer.config is set to
"http://reportingserver.domain.com/ReportServer" (DNS name of the server as
opposed to NetBIOS name). Is there a way to prevent this prefix from being
applied?
Thanks,
Sean CarpenterHello Sean,
How about use the full server url in the "Jump to URL" ?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||I am using the full URL in the Jump to URL expression. For example, a Jump
to URL of:
http://reportingserver.domain.com/ReportServer/?/ReportDirectory/AnotherReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=False&rc:ToolBar=True&Year=2006&Month=12&rc:LinkTarget=_main
Gets changed to:
http://reportingserver.domain.com/Reports/Pages/Report.aspx?ServerUrl=http%3a%2f%2freportingserver.domain.com%2fReportServer%3f%2fReportDirectory%2fAnotherReport%26rs%3aCommand%3dRender%26rs%3aformat%3dHTML4.0%26rc%3aParameters%3dFalse%26rc%3aToolBar%3dTrue%26Year%3d2006%26Month%3d12%26rc%3aLinkTarget%3d_main%26rc%253aReplacementRoot%3dhttp%253a%252f%252freportingserver.domain.com%252fReports%252fPages%252fReport.aspx%253fServerUrl%253d
It looks like the problem only occurs when the destination URL has the same
machine name as the URLRoot element of the RSReportServer.config file. Is
there any way to prevent this from happening?
Sean Carpenter
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:xNZMu4uMHHA.4020@.TK2MSFTNGHUB02.phx.gbl...
> Hello Sean,
> How about use the full server url in the "Jump to URL" ?
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ==================================================> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||Do the following. I think not only does it get around your problem but it
allows you to not hard code any server names:
=Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
This does csv in ascii format but you can change how you want.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Sean Carpenter" <stcarpenter2005@.community.nospam> wrote in message
news:%23qoKwwzMHHA.1252@.TK2MSFTNGP02.phx.gbl...
>I am using the full URL in the Jump to URL expression. For example, a Jump
>to URL of:
> http://reportingserver.domain.com/ReportServer/?/ReportDirectory/AnotherReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=False&rc:ToolBar=True&Year=2006&Month=12&rc:LinkTarget=_main
> Gets changed to:
> http://reportingserver.domain.com/Reports/Pages/Report.aspx?ServerUrl=http%3a%2f%2freportingserver.domain.com%2fReportServer%3f%2fReportDirectory%2fAnotherReport%26rs%3aCommand%3dRender%26rs%3aformat%3dHTML4.0%26rc%3aParameters%3dFalse%26rc%3aToolBar%3dTrue%26Year%3d2006%26Month%3d12%26rc%3aLinkTarget%3d_main%26rc%253aReplacementRoot%3dhttp%253a%252f%252freportingserver.domain.com%252fReports%252fPages%252fReport.aspx%253fServerUrl%253d
> It looks like the problem only occurs when the destination URL has the
> same machine name as the URLRoot element of the RSReportServer.config
> file. Is there any way to prevent this from happening?
> Sean Carpenter
>
> "Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
> news:xNZMu4uMHHA.4020@.TK2MSFTNGHUB02.phx.gbl...
>> Hello Sean,
>> How about use the full server url in the "Jump to URL" ?
>> Sincerely,
>> Wei Lu
>> Microsoft Online Community Support
>> ==================================================>> Get notification to my posts through email? Please refer to
>> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
>> ications.
>> Note: The MSDN Managed Newsgroup support offering is for non-urgent
>> issues
>> where an initial response from the community or a Microsoft Support
>> Engineer within 1 business day is acceptable. Please note that each
>> follow
>> up response may take approximately 2 business days as the support
>> professional working with you may need further investigation to reach the
>> most efficient resolution. The offering is not appropriate for situations
>> that require urgent, real-time or phone-based interactions or complex
>> project analysis and dump analysis issues. Issues of this nature are best
>> handled working with a dedicated Microsoft Support Engineer by contacting
>> Microsoft Customer Support Services (CSS) at
>> http://msdn.microsoft.com/subscriptions/support/default.aspx.
>> ==================================================>> (This posting is provided "AS IS", with no warranties, and confers no
>> rights.)
>|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
same reporting services instance. The problem I'm having is that when RS
renders the report, it changes the URL to include a prefix of
"http://reportingserver.domain.com/Reports/Pages/Report.aspx?ServerUrl=".
This is then followed by the actual URL I want to jump to. However, I don't
want this prefix to be applied. It seems to only happen when the
destination of the jump is the reporting server - if I jump to another of
our web servers, the prefix isn't applied.
I am running RS 2000 SP2 on Windows 2000 Advanced Server SP4. Also, the
URLRoot element in RSReportServer.config is set to
"http://reportingserver.domain.com/ReportServer" (DNS name of the server as
opposed to NetBIOS name). Is there a way to prevent this prefix from being
applied?
Thanks,
Sean CarpenterHello Sean,
How about use the full server url in the "Jump to URL" ?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================(This posting is provided "AS IS", with no warranties, and confers no
rights.)|||I am using the full URL in the Jump to URL expression. For example, a Jump
to URL of:
http://reportingserver.domain.com/ReportServer/?/ReportDirectory/AnotherReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=False&rc:ToolBar=True&Year=2006&Month=12&rc:LinkTarget=_main
Gets changed to:
http://reportingserver.domain.com/Reports/Pages/Report.aspx?ServerUrl=http%3a%2f%2freportingserver.domain.com%2fReportServer%3f%2fReportDirectory%2fAnotherReport%26rs%3aCommand%3dRender%26rs%3aformat%3dHTML4.0%26rc%3aParameters%3dFalse%26rc%3aToolBar%3dTrue%26Year%3d2006%26Month%3d12%26rc%3aLinkTarget%3d_main%26rc%253aReplacementRoot%3dhttp%253a%252f%252freportingserver.domain.com%252fReports%252fPages%252fReport.aspx%253fServerUrl%253d
It looks like the problem only occurs when the destination URL has the same
machine name as the URLRoot element of the RSReportServer.config file. Is
there any way to prevent this from happening?
Sean Carpenter
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:xNZMu4uMHHA.4020@.TK2MSFTNGHUB02.phx.gbl...
> Hello Sean,
> How about use the full server url in the "Jump to URL" ?
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> Get notification to my posts through email? Please refer to
> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
> ications.
> Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
> where an initial response from the community or a Microsoft Support
> Engineer within 1 business day is acceptable. Please note that each follow
> up response may take approximately 2 business days as the support
> professional working with you may need further investigation to reach the
> most efficient resolution. The offering is not appropriate for situations
> that require urgent, real-time or phone-based interactions or complex
> project analysis and dump analysis issues. Issues of this nature are best
> handled working with a dedicated Microsoft Support Engineer by contacting
> Microsoft Customer Support Services (CSS) at
> http://msdn.microsoft.com/subscriptions/support/default.aspx.
> ==================================================> (This posting is provided "AS IS", with no warranties, and confers no
> rights.)
>|||Do the following. I think not only does it get around your problem but it
allows you to not hard code any server names:
=Globals!ReportServerUrl & "?/SomeFolder/SomeReport&ParamName=" &
Parameters!ParamName.Value & "&rs:Format=CSV&rc:Encoding=ASCII"
This does csv in ascii format but you can change how you want.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Sean Carpenter" <stcarpenter2005@.community.nospam> wrote in message
news:%23qoKwwzMHHA.1252@.TK2MSFTNGP02.phx.gbl...
>I am using the full URL in the Jump to URL expression. For example, a Jump
>to URL of:
> http://reportingserver.domain.com/ReportServer/?/ReportDirectory/AnotherReport&rs:Command=Render&rs:format=HTML4.0&rc:Parameters=False&rc:ToolBar=True&Year=2006&Month=12&rc:LinkTarget=_main
> Gets changed to:
> http://reportingserver.domain.com/Reports/Pages/Report.aspx?ServerUrl=http%3a%2f%2freportingserver.domain.com%2fReportServer%3f%2fReportDirectory%2fAnotherReport%26rs%3aCommand%3dRender%26rs%3aformat%3dHTML4.0%26rc%3aParameters%3dFalse%26rc%3aToolBar%3dTrue%26Year%3d2006%26Month%3d12%26rc%3aLinkTarget%3d_main%26rc%253aReplacementRoot%3dhttp%253a%252f%252freportingserver.domain.com%252fReports%252fPages%252fReport.aspx%253fServerUrl%253d
> It looks like the problem only occurs when the destination URL has the
> same machine name as the URLRoot element of the RSReportServer.config
> file. Is there any way to prevent this from happening?
> Sean Carpenter
>
> "Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
> news:xNZMu4uMHHA.4020@.TK2MSFTNGHUB02.phx.gbl...
>> Hello Sean,
>> How about use the full server url in the "Jump to URL" ?
>> Sincerely,
>> Wei Lu
>> Microsoft Online Community Support
>> ==================================================>> Get notification to my posts through email? Please refer to
>> http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
>> ications.
>> Note: The MSDN Managed Newsgroup support offering is for non-urgent
>> issues
>> where an initial response from the community or a Microsoft Support
>> Engineer within 1 business day is acceptable. Please note that each
>> follow
>> up response may take approximately 2 business days as the support
>> professional working with you may need further investigation to reach the
>> most efficient resolution. The offering is not appropriate for situations
>> that require urgent, real-time or phone-based interactions or complex
>> project analysis and dump analysis issues. Issues of this nature are best
>> handled working with a dedicated Microsoft Support Engineer by contacting
>> Microsoft Customer Support Services (CSS) at
>> http://msdn.microsoft.com/subscriptions/support/default.aspx.
>> ==================================================>> (This posting is provided "AS IS", with no warranties, and confers no
>> rights.)
>|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Jump To URL Bug
I have two different URLs I use for Jump To URL navigation in my
reports.
This one adds a String report parameter on the end and works fine:
=Globals!ReportServerUrl + Globals!ReportFolder +
"?/Detail/Campaign+List&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false&rc:Zoom=Whole+Page&rc:Parameters=false&CampaignCode="
+ Fields!CampaignCode.Value
This one adds an Integer report parameter on the end and does not
work:
=Globals!ReportServerUrl + Globals!ReportFolder +
"?/Detail/Order+Detail&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false&rc:Zoom=Whole+Page&rc:Parameters=false&OrderID="
+ Fields!OrderID.Value
The two URLs are exactly the same except for the report names and
report parameters passed on the end. For some reason the second URL
that passes an Integer report parameter does not create a Hyperlink at
all, you can't click on it. If you remove the #"&OrderID=" +
Fields!OrderID.Value# (#'s used for reference only) part the field
will become a Hyperlink, but of course the report won't run because it
needs the report parameter passed. I also tried sticking it in the
middle of the URL and still
no dice.
The only conclusion I can come to is that there is a bug passing an
Integer parameter in the Jump To URL. Can someone run a quick test
that replicates this problem and confirm or deny this as being a bug?
Any and all help is appreciated.
FrankFrank,
Use an & instead of the + to concatenate the URL strings. I saw the bug
happen when there is a + sign. When I used the &, it works fine.
"Stoma_Kalos" <fzuma@.yahoo.com> wrote in message
news:e876e3c8.0411231419.5a269fa8@.posting.google.com...
> I have two different URLs I use for Jump To URL navigation in my
> reports.
> This one adds a String report parameter on the end and works fine:
> =Globals!ReportServerUrl + Globals!ReportFolder +
>
"?/Detail/Campaign+List&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false
&rc:Zoom=Whole+Page&rc:Parameters=false&CampaignCode="
> + Fields!CampaignCode.Value
> This one adds an Integer report parameter on the end and does not
> work:
> =Globals!ReportServerUrl + Globals!ReportFolder +
>
"?/Detail/Order+Detail&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false&
rc:Zoom=Whole+Page&rc:Parameters=false&OrderID="
> + Fields!OrderID.Value
> The two URLs are exactly the same except for the report names and
> report parameters passed on the end. For some reason the second URL
> that passes an Integer report parameter does not create a Hyperlink at
> all, you can't click on it. If you remove the #"&OrderID=" +
> Fields!OrderID.Value# (#'s used for reference only) part the field
> will become a Hyperlink, but of course the report won't run because it
> needs the report parameter passed. I also tried sticking it in the
> middle of the URL and still
> no dice.
> The only conclusion I can come to is that there is a bug passing an
> Integer parameter in the Jump To URL. Can someone run a quick test
> that replicates this problem and confirm or deny this as being a bug?
> Any and all help is appreciated.
> Frank|||What is happening is when you use a + it does a concatenate if they are
strings. If it sees a number it trys to add it (this is a vb thing). Always
use & when concatenating strings.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stoma_Kalos" <fzuma@.yahoo.com> wrote in message
news:e876e3c8.0411231419.5a269fa8@.posting.google.com...
> I have two different URLs I use for Jump To URL navigation in my
> reports.
> This one adds a String report parameter on the end and works fine:
> =Globals!ReportServerUrl + Globals!ReportFolder +
>
"?/Detail/Campaign+List&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false
&rc:Zoom=Whole+Page&rc:Parameters=false&CampaignCode="
> + Fields!CampaignCode.Value
> This one adds an Integer report parameter on the end and does not
> work:
> =Globals!ReportServerUrl + Globals!ReportFolder +
>
"?/Detail/Order+Detail&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false&
rc:Zoom=Whole+Page&rc:Parameters=false&OrderID="
> + Fields!OrderID.Value
> The two URLs are exactly the same except for the report names and
> report parameters passed on the end. For some reason the second URL
> that passes an Integer report parameter does not create a Hyperlink at
> all, you can't click on it. If you remove the #"&OrderID=" +
> Fields!OrderID.Value# (#'s used for reference only) part the field
> will become a Hyperlink, but of course the report won't run because it
> needs the report parameter passed. I also tried sticking it in the
> middle of the URL and still
> no dice.
> The only conclusion I can come to is that there is a bug passing an
> Integer parameter in the Jump To URL. Can someone run a quick test
> that replicates this problem and confirm or deny this as being a bug?
> Any and all help is appreciated.
> Frank|||I appreciate both of ya'lls help...I've spent way too much time on
that problem. Thanks!!!
Frank
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message news:<#V2B7Gb0EHA.3336@.TK2MSFTNGP11.phx.gbl>...
> What is happening is when you use a + it does a concatenate if they are
> strings. If it sees a number it trys to add it (this is a vb thing). Always
> use & when concatenating strings.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services|||Just a FYI: the difference between + and & is that a concatenation using &
will implicitly call the .ToString() method on the object before
concatenation.
Concatenating real strings will also work with + instead of &
e.g. ="Hello " + "World"
For other datatypes, you could also use CStr() to convert them to strings:
e.g. =CStr(20)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Stoma_Kalos" <fzuma@.yahoo.com> wrote in message
news:e876e3c8.0411291255.3b9241e8@.posting.google.com...
> I appreciate both of ya'lls help...I've spent way too much time on
> that problem. Thanks!!!
> Frank
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:<#V2B7Gb0EHA.3336@.TK2MSFTNGP11.phx.gbl>...
> > What is happening is when you use a + it does a concatenate if they are
> > strings. If it sees a number it trys to add it (this is a vb thing).
Always
> > use & when concatenating strings.
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
reports.
This one adds a String report parameter on the end and works fine:
=Globals!ReportServerUrl + Globals!ReportFolder +
"?/Detail/Campaign+List&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false&rc:Zoom=Whole+Page&rc:Parameters=false&CampaignCode="
+ Fields!CampaignCode.Value
This one adds an Integer report parameter on the end and does not
work:
=Globals!ReportServerUrl + Globals!ReportFolder +
"?/Detail/Order+Detail&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false&rc:Zoom=Whole+Page&rc:Parameters=false&OrderID="
+ Fields!OrderID.Value
The two URLs are exactly the same except for the report names and
report parameters passed on the end. For some reason the second URL
that passes an Integer report parameter does not create a Hyperlink at
all, you can't click on it. If you remove the #"&OrderID=" +
Fields!OrderID.Value# (#'s used for reference only) part the field
will become a Hyperlink, but of course the report won't run because it
needs the report parameter passed. I also tried sticking it in the
middle of the URL and still
no dice.
The only conclusion I can come to is that there is a bug passing an
Integer parameter in the Jump To URL. Can someone run a quick test
that replicates this problem and confirm or deny this as being a bug?
Any and all help is appreciated.
FrankFrank,
Use an & instead of the + to concatenate the URL strings. I saw the bug
happen when there is a + sign. When I used the &, it works fine.
"Stoma_Kalos" <fzuma@.yahoo.com> wrote in message
news:e876e3c8.0411231419.5a269fa8@.posting.google.com...
> I have two different URLs I use for Jump To URL navigation in my
> reports.
> This one adds a String report parameter on the end and works fine:
> =Globals!ReportServerUrl + Globals!ReportFolder +
>
"?/Detail/Campaign+List&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false
&rc:Zoom=Whole+Page&rc:Parameters=false&CampaignCode="
> + Fields!CampaignCode.Value
> This one adds an Integer report parameter on the end and does not
> work:
> =Globals!ReportServerUrl + Globals!ReportFolder +
>
"?/Detail/Order+Detail&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false&
rc:Zoom=Whole+Page&rc:Parameters=false&OrderID="
> + Fields!OrderID.Value
> The two URLs are exactly the same except for the report names and
> report parameters passed on the end. For some reason the second URL
> that passes an Integer report parameter does not create a Hyperlink at
> all, you can't click on it. If you remove the #"&OrderID=" +
> Fields!OrderID.Value# (#'s used for reference only) part the field
> will become a Hyperlink, but of course the report won't run because it
> needs the report parameter passed. I also tried sticking it in the
> middle of the URL and still
> no dice.
> The only conclusion I can come to is that there is a bug passing an
> Integer parameter in the Jump To URL. Can someone run a quick test
> that replicates this problem and confirm or deny this as being a bug?
> Any and all help is appreciated.
> Frank|||What is happening is when you use a + it does a concatenate if they are
strings. If it sees a number it trys to add it (this is a vb thing). Always
use & when concatenating strings.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Stoma_Kalos" <fzuma@.yahoo.com> wrote in message
news:e876e3c8.0411231419.5a269fa8@.posting.google.com...
> I have two different URLs I use for Jump To URL navigation in my
> reports.
> This one adds a String report parameter on the end and works fine:
> =Globals!ReportServerUrl + Globals!ReportFolder +
>
"?/Detail/Campaign+List&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false
&rc:Zoom=Whole+Page&rc:Parameters=false&CampaignCode="
> + Fields!CampaignCode.Value
> This one adds an Integer report parameter on the end and does not
> work:
> =Globals!ReportServerUrl + Globals!ReportFolder +
>
"?/Detail/Order+Detail&rs:Command=Render&rs:format=HTML4.0&rc:Toolbar=false&
rc:Zoom=Whole+Page&rc:Parameters=false&OrderID="
> + Fields!OrderID.Value
> The two URLs are exactly the same except for the report names and
> report parameters passed on the end. For some reason the second URL
> that passes an Integer report parameter does not create a Hyperlink at
> all, you can't click on it. If you remove the #"&OrderID=" +
> Fields!OrderID.Value# (#'s used for reference only) part the field
> will become a Hyperlink, but of course the report won't run because it
> needs the report parameter passed. I also tried sticking it in the
> middle of the URL and still
> no dice.
> The only conclusion I can come to is that there is a bug passing an
> Integer parameter in the Jump To URL. Can someone run a quick test
> that replicates this problem and confirm or deny this as being a bug?
> Any and all help is appreciated.
> Frank|||I appreciate both of ya'lls help...I've spent way too much time on
that problem. Thanks!!!
Frank
"Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message news:<#V2B7Gb0EHA.3336@.TK2MSFTNGP11.phx.gbl>...
> What is happening is when you use a + it does a concatenate if they are
> strings. If it sees a number it trys to add it (this is a vb thing). Always
> use & when concatenating strings.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services|||Just a FYI: the difference between + and & is that a concatenation using &
will implicitly call the .ToString() method on the object before
concatenation.
Concatenating real strings will also work with + instead of &
e.g. ="Hello " + "World"
For other datatypes, you could also use CStr() to convert them to strings:
e.g. =CStr(20)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Stoma_Kalos" <fzuma@.yahoo.com> wrote in message
news:e876e3c8.0411291255.3b9241e8@.posting.google.com...
> I appreciate both of ya'lls help...I've spent way too much time on
> that problem. Thanks!!!
> Frank
> "Bruce L-C [MVP]" <bruce_lcNOSPAM@.hotmail.com> wrote in message
news:<#V2B7Gb0EHA.3336@.TK2MSFTNGP11.phx.gbl>...
> > What is happening is when you use a + it does a concatenate if they are
> > strings. If it sees a number it trys to add it (this is a vb thing).
Always
> > use & when concatenating strings.
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
Jump to URL - Javascript
We are displaying reports in a PDF format through an aspx page.
I have put and URL link in an report as follows to open a new
window(cotaining another report)
="javascript:void(window.open('http://localhost/ReportViewer/ReportFrame.aspx?rptPath=REPORTPATH&args="
& REPORTARGS &
"','GraphDetail','left=50,top=50,width=800,height=580,menubar=no,resizable=yes,scrollbars=Yes,status=yes,toolbar=0'))"
When the report is displayed for the first time...the URL link works fine. I
get an security msg from adobe reader saying document is trying to open this
link ..asks to block or allow...when i click Allow ..the new window
opens(with the report). But when i close this new window and reclick the
link...it does not work.
I have been stuck in this for 4 days now...i am not getting what is the
issue...
The aspx page has frames...but i do not see any issue with that either...i
am tried with a simple aspx page...same issue...i have tried allowing
pop-ups ...etc
I think this is issue with adobe reader ..because if i display the report
in HTML format...the link works fine...opens every time i click it!!!!.
Has anyone has had any similar issues!!!!...
Can anyone help me ...all i want to do is...open a link in new window from
an deployed PDF report ...link is an aspx page with a new detail report.
Thanks.Hi,
my jump to link is similar and working.
my link is like this..
="javascript:" &
IIF(Fields!Acked.Value = 1,"void(0)",
"var sRS='" & Globals!ReportServerUrl &
"';void(window.open(sRS.substring(0,sRS.indexOf('/ReportServer')) +
'/rtreporting/acknowledge.aspx?FilterID=" & Fields!FILTERID.Value &
"&prmServer=" & Fields!SERVER.Value & "&prmStartDate=" &
Format(Parameters!prmDateFrom.Value,"yyyy-MM-dd HH:mm:ss") & "&prmEndDate=" &
Format(Parameters!prmDateTo.Value,"yyyy-MM-dd HH:mm:ss") & "','_blank'))")
can you use Globals!ReportServerUrl instead of localhost.
also try using _blank parameter and make it default size..
"Sunny" wrote:
> We are displaying reports in a PDF format through an aspx page.
> I have put and URL link in an report as follows to open a new
> window(cotaining another report)
> ="javascript:void(window.open('http://localhost/ReportViewer/ReportFrame.aspx?rptPath=REPORTPATH&args="
> & REPORTARGS &
> "','GraphDetail','left=50,top=50,width=800,height=580,menubar=no,resizable=yes,scrollbars=Yes,status=yes,toolbar=0'))"
>
> When the report is displayed for the first time...the URL link works fine. I
> get an security msg from adobe reader saying document is trying to open this
> link ..asks to block or allow...when i click Allow ..the new window
> opens(with the report). But when i close this new window and reclick the
> link...it does not work.
> I have been stuck in this for 4 days now...i am not getting what is the
> issue...
> The aspx page has frames...but i do not see any issue with that either...i
> am tried with a simple aspx page...same issue...i have tried allowing
> pop-ups ...etc
> I think this is issue with adobe reader ..because if i display the report
> in HTML format...the link works fine...opens every time i click it!!!!.
> Has anyone has had any similar issues!!!!...
> Can anyone help me ...all i want to do is...open a link in new window from
> an deployed PDF report ...link is an aspx page with a new detail report.
> Thanks.
I have put and URL link in an report as follows to open a new
window(cotaining another report)
="javascript:void(window.open('http://localhost/ReportViewer/ReportFrame.aspx?rptPath=REPORTPATH&args="
& REPORTARGS &
"','GraphDetail','left=50,top=50,width=800,height=580,menubar=no,resizable=yes,scrollbars=Yes,status=yes,toolbar=0'))"
When the report is displayed for the first time...the URL link works fine. I
get an security msg from adobe reader saying document is trying to open this
link ..asks to block or allow...when i click Allow ..the new window
opens(with the report). But when i close this new window and reclick the
link...it does not work.
I have been stuck in this for 4 days now...i am not getting what is the
issue...
The aspx page has frames...but i do not see any issue with that either...i
am tried with a simple aspx page...same issue...i have tried allowing
pop-ups ...etc
I think this is issue with adobe reader ..because if i display the report
in HTML format...the link works fine...opens every time i click it!!!!.
Has anyone has had any similar issues!!!!...
Can anyone help me ...all i want to do is...open a link in new window from
an deployed PDF report ...link is an aspx page with a new detail report.
Thanks.Hi,
my jump to link is similar and working.
my link is like this..
="javascript:" &
IIF(Fields!Acked.Value = 1,"void(0)",
"var sRS='" & Globals!ReportServerUrl &
"';void(window.open(sRS.substring(0,sRS.indexOf('/ReportServer')) +
'/rtreporting/acknowledge.aspx?FilterID=" & Fields!FILTERID.Value &
"&prmServer=" & Fields!SERVER.Value & "&prmStartDate=" &
Format(Parameters!prmDateFrom.Value,"yyyy-MM-dd HH:mm:ss") & "&prmEndDate=" &
Format(Parameters!prmDateTo.Value,"yyyy-MM-dd HH:mm:ss") & "','_blank'))")
can you use Globals!ReportServerUrl instead of localhost.
also try using _blank parameter and make it default size..
"Sunny" wrote:
> We are displaying reports in a PDF format through an aspx page.
> I have put and URL link in an report as follows to open a new
> window(cotaining another report)
> ="javascript:void(window.open('http://localhost/ReportViewer/ReportFrame.aspx?rptPath=REPORTPATH&args="
> & REPORTARGS &
> "','GraphDetail','left=50,top=50,width=800,height=580,menubar=no,resizable=yes,scrollbars=Yes,status=yes,toolbar=0'))"
>
> When the report is displayed for the first time...the URL link works fine. I
> get an security msg from adobe reader saying document is trying to open this
> link ..asks to block or allow...when i click Allow ..the new window
> opens(with the report). But when i close this new window and reclick the
> link...it does not work.
> I have been stuck in this for 4 days now...i am not getting what is the
> issue...
> The aspx page has frames...but i do not see any issue with that either...i
> am tried with a simple aspx page...same issue...i have tried allowing
> pop-ups ...etc
> I think this is issue with adobe reader ..because if i display the report
> in HTML format...the link works fine...opens every time i click it!!!!.
> Has anyone has had any similar issues!!!!...
> Can anyone help me ...all i want to do is...open a link in new window from
> an deployed PDF report ...link is an aspx page with a new detail report.
> Thanks.
Wednesday, March 28, 2012
Jump to URL
Hi,
I have made a report consisting of links to other reports. I open the links via the "Jump to URL" functionality. Is there any way of opening the links in seperate browser windows? My users would like to be able to have more than one report open at a time.
Thanks for any help :-)
-- Heidi --
You can use javascript function instead of a report name.try to use the window.open function.
try to write:
javascript:window.open('URL');
change URL to your url or report.|||My links are defined in a table as a simple textbox with navigation. How can I insert javascript to this code?|||
Now I have the following in my jump to url:
= window.open(Fields!filename.Value)"
where Fields!filename.Value contains the URL to my reports.
When I click the link I get an error saying " ) expected"
My links look something like this:
http://myserver/ReportServer$SQL2005/Pages/ReportViewer.aspx?%2fStandard+reports%2fIDPointActivity&rs%3aClearSession=true&rc%3aView=45ec7368-1fb0-4313-8235-2ae1110bb9ca
Any idea what I am doing wrong?
I can make the link work, when I type in the url-directly as parameter to the window.open-function - this is not a solution for me though, since I need to use dynamic links retrieved from a database.
Jump to report value for parameter, cube data
Have a problem with passing information between reports using Jump to report
facility.
User clicking on field value in report to pass to second report. This works
with the second report showing the value of field user has selected in the
parameter box (Available Values set to non-queried) but report shows an error
of:
restrictions imposed by the constrained flag in the STRTOSET function were
violated
Have tried many settings to correct this but with no luck. Does anybody
know how to correct this problem.
Thanks
IanIn case this is helpful to others I have found that the field parameter was
causing the problem. I was using Fields!FieldName.Value and should have used
Fields!FieldName.UniqueName
Ian
"IanP" wrote:
> Have a problem with passing information between reports using Jump to report
> facility.
> User clicking on field value in report to pass to second report. This works
> with the second report showing the value of field user has selected in the
> parameter box (Available Values set to non-queried) but report shows an error
> of:
> restrictions imposed by the constrained flag in the STRTOSET function were
> violated
> Have tried many settings to correct this but with no luck. Does anybody
> know how to correct this problem.
> Thanks
> Ian
facility.
User clicking on field value in report to pass to second report. This works
with the second report showing the value of field user has selected in the
parameter box (Available Values set to non-queried) but report shows an error
of:
restrictions imposed by the constrained flag in the STRTOSET function were
violated
Have tried many settings to correct this but with no luck. Does anybody
know how to correct this problem.
Thanks
IanIn case this is helpful to others I have found that the field parameter was
causing the problem. I was using Fields!FieldName.Value and should have used
Fields!FieldName.UniqueName
Ian
"IanP" wrote:
> Have a problem with passing information between reports using Jump to report
> facility.
> User clicking on field value in report to pass to second report. This works
> with the second report showing the value of field user has selected in the
> parameter box (Available Values set to non-queried) but report shows an error
> of:
> restrictions imposed by the constrained flag in the STRTOSET function were
> violated
> Have tried many settings to correct this but with no luck. Does anybody
> know how to correct this problem.
> Thanks
> Ian
Jump to Report Not Functioning Correctly
Hi all,
I'm having a problem with a series of reports I'm developing that allow the
user to design their own reports. They involve passing parameters (and
sometimes not passing parameters) between many different reports. The issue
I have is this:
I have an opening page with no parameters. When I jump to the next report
(using Jump to Report in Properties -> Navigation tab) it begins to load the
next report, but the parameter bar is missing (not hidden) and the report
itself doesn't load (although the report title is displayed in the top
frame).
If I use "Jump To URL", these issues appear to be less of a problem but
passing parameters is more difficult.
A couple of questions for you:
1) Has anyone else experienced this issue?
2) How can I pass parameters in a Jump to URL string, based on either report
parameters or report datasets?
I've had a look around on the forums and have found some similar problems,
which is why I ended up looking at the Jump to URL option. I haven't found
anyone with the same issue though. Can anyone help?!
Thanks in advance,
JonA little more information for you.
I've been trying to diagnose the issue, and I thought the problem was due to
passing parameters between reports but it now appears this isn't the case.
I have one report that has a subreport containing jumps to four other
reports. 3 of the reports do not work, but one does. None of the reports
require parameters to be passed, but the 3 that do not work have a parameter
that requires selection before the report will be shown.
If I place a default value in the report I'm jumping to, for the parameter
being passed (in this case, an ID for the report) it works fine. So the
issue appears to be when there is no default value for the parameter in the
report I'm jumping to. Unfortunately, I can't just set a default value in
this case.
Has anyone come across this or know a workaround other than setting a
default?
Thanks again,
Jon
"Jonathan Martin" <jonathan.martin@.pcservicecall.co.uk> wrote in message
news:%23SQ6CYsNFHA.3188@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> I'm having a problem with a series of reports I'm developing that allow
> the user to design their own reports. They involve passing parameters
> (and sometimes not passing parameters) between many different reports.
> The issue I have is this:
> I have an opening page with no parameters. When I jump to the next report
> (using Jump to Report in Properties -> Navigation tab) it begins to load
> the next report, but the parameter bar is missing (not hidden) and the
> report itself doesn't load (although the report title is displayed in the
> top frame).
> If I use "Jump To URL", these issues appear to be less of a problem but
> passing parameters is more difficult.
> A couple of questions for you:
> 1) Has anyone else experienced this issue?
> 2) How can I pass parameters in a Jump to URL string, based on either
> report parameters or report datasets?
> I've had a look around on the forums and have found some similar problems,
> which is why I ended up looking at the Jump to URL option. I haven't
> found anyone with the same issue though. Can anyone help?!
> Thanks in advance,
>
> Jon
>|||you have to set all parameters for the reports you are jumping to. This is
easier with the "Jump to Report" option - just click the Parameters button.
You can set hardcoded values are use other report items as input parameters.
For URL jumps - use "?paramenter_name=parameter_value" after the URL address
"Jonathan Martin" wrote:
> A little more information for you.
> I've been trying to diagnose the issue, and I thought the problem was due to
> passing parameters between reports but it now appears this isn't the case.
> I have one report that has a subreport containing jumps to four other
> reports. 3 of the reports do not work, but one does. None of the reports
> require parameters to be passed, but the 3 that do not work have a parameter
> that requires selection before the report will be shown.
> If I place a default value in the report I'm jumping to, for the parameter
> being passed (in this case, an ID for the report) it works fine. So the
> issue appears to be when there is no default value for the parameter in the
> report I'm jumping to. Unfortunately, I can't just set a default value in
> this case.
> Has anyone come across this or know a workaround other than setting a
> default?
> Thanks again,
>
> Jon
>
> "Jonathan Martin" <jonathan.martin@.pcservicecall.co.uk> wrote in message
> news:%23SQ6CYsNFHA.3188@.TK2MSFTNGP10.phx.gbl...
> > Hi all,
> >
> > I'm having a problem with a series of reports I'm developing that allow
> > the user to design their own reports. They involve passing parameters
> > (and sometimes not passing parameters) between many different reports.
> > The issue I have is this:
> >
> > I have an opening page with no parameters. When I jump to the next report
> > (using Jump to Report in Properties -> Navigation tab) it begins to load
> > the next report, but the parameter bar is missing (not hidden) and the
> > report itself doesn't load (although the report title is displayed in the
> > top frame).
> >
> > If I use "Jump To URL", these issues appear to be less of a problem but
> > passing parameters is more difficult.
> >
> > A couple of questions for you:
> >
> > 1) Has anyone else experienced this issue?
> > 2) How can I pass parameters in a Jump to URL string, based on either
> > report parameters or report datasets?
> >
> > I've had a look around on the forums and have found some similar problems,
> > which is why I ended up looking at the Jump to URL option. I haven't
> > found anyone with the same issue though. Can anyone help?!
> >
> > Thanks in advance,
> >
> >
> > Jon
> >
>
>|||Unfortunately it's still causing issues with passing the parameter values.
It does work fine with passing the parameter through the URL though.
No idea why, but it's working!
Thanks for the help.
"jj#10" <jj10@.discussions.microsoft.com> wrote in message
news:DDB82610-A1B2-4518-AB28-20D55D6B4BEF@.microsoft.com...
> you have to set all parameters for the reports you are jumping to. This
> is
> easier with the "Jump to Report" option - just click the Parameters
> button.
> You can set hardcoded values are use other report items as input
> parameters.
> For URL jumps - use "?paramenter_name=parameter_value" after the URL
> address
> "Jonathan Martin" wrote:
>> A little more information for you.
>> I've been trying to diagnose the issue, and I thought the problem was due
>> to
>> passing parameters between reports but it now appears this isn't the
>> case.
>> I have one report that has a subreport containing jumps to four other
>> reports. 3 of the reports do not work, but one does. None of the
>> reports
>> require parameters to be passed, but the 3 that do not work have a
>> parameter
>> that requires selection before the report will be shown.
>> If I place a default value in the report I'm jumping to, for the
>> parameter
>> being passed (in this case, an ID for the report) it works fine. So the
>> issue appears to be when there is no default value for the parameter in
>> the
>> report I'm jumping to. Unfortunately, I can't just set a default value
>> in
>> this case.
>> Has anyone come across this or know a workaround other than setting a
>> default?
>> Thanks again,
>>
>> Jon
>>
>> "Jonathan Martin" <jonathan.martin@.pcservicecall.co.uk> wrote in message
>> news:%23SQ6CYsNFHA.3188@.TK2MSFTNGP10.phx.gbl...
>> > Hi all,
>> >
>> > I'm having a problem with a series of reports I'm developing that allow
>> > the user to design their own reports. They involve passing parameters
>> > (and sometimes not passing parameters) between many different reports.
>> > The issue I have is this:
>> >
>> > I have an opening page with no parameters. When I jump to the next
>> > report
>> > (using Jump to Report in Properties -> Navigation tab) it begins to
>> > load
>> > the next report, but the parameter bar is missing (not hidden) and the
>> > report itself doesn't load (although the report title is displayed in
>> > the
>> > top frame).
>> >
>> > If I use "Jump To URL", these issues appear to be less of a problem but
>> > passing parameters is more difficult.
>> >
>> > A couple of questions for you:
>> >
>> > 1) Has anyone else experienced this issue?
>> > 2) How can I pass parameters in a Jump to URL string, based on either
>> > report parameters or report datasets?
>> >
>> > I've had a look around on the forums and have found some similar
>> > problems,
>> > which is why I ended up looking at the Jump to URL option. I haven't
>> > found anyone with the same issue though. Can anyone help?!
>> >
>> > Thanks in advance,
>> >
>> >
>> > Jon
>> >
>>|||I am having a similar problem, but I use jump to report and it works fine in
development environment (i.e. visual studio), but does not work live.
"Jonathan Martin" wrote:
> Unfortunately it's still causing issues with passing the parameter values.
> It does work fine with passing the parameter through the URL though.
> No idea why, but it's working!
> Thanks for the help.
> "jj#10" <jj10@.discussions.microsoft.com> wrote in message
> news:DDB82610-A1B2-4518-AB28-20D55D6B4BEF@.microsoft.com...
> > you have to set all parameters for the reports you are jumping to. This
> > is
> > easier with the "Jump to Report" option - just click the Parameters
> > button.
> > You can set hardcoded values are use other report items as input
> > parameters.
> >
> > For URL jumps - use "?paramenter_name=parameter_value" after the URL
> > address
> >
> > "Jonathan Martin" wrote:
> >
> >> A little more information for you.
> >>
> >> I've been trying to diagnose the issue, and I thought the problem was due
> >> to
> >> passing parameters between reports but it now appears this isn't the
> >> case.
> >>
> >> I have one report that has a subreport containing jumps to four other
> >> reports. 3 of the reports do not work, but one does. None of the
> >> reports
> >> require parameters to be passed, but the 3 that do not work have a
> >> parameter
> >> that requires selection before the report will be shown.
> >>
> >> If I place a default value in the report I'm jumping to, for the
> >> parameter
> >> being passed (in this case, an ID for the report) it works fine. So the
> >> issue appears to be when there is no default value for the parameter in
> >> the
> >> report I'm jumping to. Unfortunately, I can't just set a default value
> >> in
> >> this case.
> >>
> >> Has anyone come across this or know a workaround other than setting a
> >> default?
> >>
> >> Thanks again,
> >>
> >>
> >> Jon
> >>
> >>
> >> "Jonathan Martin" <jonathan.martin@.pcservicecall.co.uk> wrote in message
> >> news:%23SQ6CYsNFHA.3188@.TK2MSFTNGP10.phx.gbl...
> >> > Hi all,
> >> >
> >> > I'm having a problem with a series of reports I'm developing that allow
> >> > the user to design their own reports. They involve passing parameters
> >> > (and sometimes not passing parameters) between many different reports.
> >> > The issue I have is this:
> >> >
> >> > I have an opening page with no parameters. When I jump to the next
> >> > report
> >> > (using Jump to Report in Properties -> Navigation tab) it begins to
> >> > load
> >> > the next report, but the parameter bar is missing (not hidden) and the
> >> > report itself doesn't load (although the report title is displayed in
> >> > the
> >> > top frame).
> >> >
> >> > If I use "Jump To URL", these issues appear to be less of a problem but
> >> > passing parameters is more difficult.
> >> >
> >> > A couple of questions for you:
> >> >
> >> > 1) Has anyone else experienced this issue?
> >> > 2) How can I pass parameters in a Jump to URL string, based on either
> >> > report parameters or report datasets?
> >> >
> >> > I've had a look around on the forums and have found some similar
> >> > problems,
> >> > which is why I ended up looking at the Jump to URL option. I haven't
> >> > found anyone with the same issue though. Can anyone help?!
> >> >
> >> > Thanks in advance,
> >> >
> >> >
> >> > Jon
> >> >
> >>
> >>
> >>
>
>|||Is the URL mapped to the correct "live" server (i.e. Not http://localhost/...)
Message posted via http://www.sqlmonster.com|||URL is mapped correctly and remember I am using "jump to report"
"Corey Crumbaugh via SQLMonster.com" wrote:
> Is the URL mapped to the correct "live" server (i.e. Not http://localhost/...)
>
> --
> Message posted via http://www.sqlmonster.com
>|||My guess is that the report in question (that you are jumping to) has a
credential problem. Can you run the report you are trying to jump to by
itself?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"bamboo" <bamboo@.discussions.microsoft.com> wrote in message
news:A1910C53-32D2-40D2-BB75-D67AF6779793@.microsoft.com...
> URL is mapped correctly and remember I am using "jump to report"
> "Corey Crumbaugh via SQLMonster.com" wrote:
>> Is the URL mapped to the correct "live" server (i.e. Not
>> http://localhost/...)
>>
>> --
>> Message posted via http://www.sqlmonster.com|||I found that the problem is the 2nd report has to be runnable right away
(i.e. cannot prompt user to enter parameters when it is being executed from
another report). This is not a good function.
Thus, this goes back to what jonathan posed.
"Bruce L-C [MVP]" wrote:
> My guess is that the report in question (that you are jumping to) has a
> credential problem. Can you run the report you are trying to jump to by
> itself?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "bamboo" <bamboo@.discussions.microsoft.com> wrote in message
> news:A1910C53-32D2-40D2-BB75-D67AF6779793@.microsoft.com...
> > URL is mapped correctly and remember I am using "jump to report"
> >
> > "Corey Crumbaugh via SQLMonster.com" wrote:
> >
> >> Is the URL mapped to the correct "live" server (i.e. Not
> >> http://localhost/...)
> >>
> >>
> >> --
> >> Message posted via http://www.sqlmonster.com
> >>
>
>
I'm having a problem with a series of reports I'm developing that allow the
user to design their own reports. They involve passing parameters (and
sometimes not passing parameters) between many different reports. The issue
I have is this:
I have an opening page with no parameters. When I jump to the next report
(using Jump to Report in Properties -> Navigation tab) it begins to load the
next report, but the parameter bar is missing (not hidden) and the report
itself doesn't load (although the report title is displayed in the top
frame).
If I use "Jump To URL", these issues appear to be less of a problem but
passing parameters is more difficult.
A couple of questions for you:
1) Has anyone else experienced this issue?
2) How can I pass parameters in a Jump to URL string, based on either report
parameters or report datasets?
I've had a look around on the forums and have found some similar problems,
which is why I ended up looking at the Jump to URL option. I haven't found
anyone with the same issue though. Can anyone help?!
Thanks in advance,
JonA little more information for you.
I've been trying to diagnose the issue, and I thought the problem was due to
passing parameters between reports but it now appears this isn't the case.
I have one report that has a subreport containing jumps to four other
reports. 3 of the reports do not work, but one does. None of the reports
require parameters to be passed, but the 3 that do not work have a parameter
that requires selection before the report will be shown.
If I place a default value in the report I'm jumping to, for the parameter
being passed (in this case, an ID for the report) it works fine. So the
issue appears to be when there is no default value for the parameter in the
report I'm jumping to. Unfortunately, I can't just set a default value in
this case.
Has anyone come across this or know a workaround other than setting a
default?
Thanks again,
Jon
"Jonathan Martin" <jonathan.martin@.pcservicecall.co.uk> wrote in message
news:%23SQ6CYsNFHA.3188@.TK2MSFTNGP10.phx.gbl...
> Hi all,
> I'm having a problem with a series of reports I'm developing that allow
> the user to design their own reports. They involve passing parameters
> (and sometimes not passing parameters) between many different reports.
> The issue I have is this:
> I have an opening page with no parameters. When I jump to the next report
> (using Jump to Report in Properties -> Navigation tab) it begins to load
> the next report, but the parameter bar is missing (not hidden) and the
> report itself doesn't load (although the report title is displayed in the
> top frame).
> If I use "Jump To URL", these issues appear to be less of a problem but
> passing parameters is more difficult.
> A couple of questions for you:
> 1) Has anyone else experienced this issue?
> 2) How can I pass parameters in a Jump to URL string, based on either
> report parameters or report datasets?
> I've had a look around on the forums and have found some similar problems,
> which is why I ended up looking at the Jump to URL option. I haven't
> found anyone with the same issue though. Can anyone help?!
> Thanks in advance,
>
> Jon
>|||you have to set all parameters for the reports you are jumping to. This is
easier with the "Jump to Report" option - just click the Parameters button.
You can set hardcoded values are use other report items as input parameters.
For URL jumps - use "?paramenter_name=parameter_value" after the URL address
"Jonathan Martin" wrote:
> A little more information for you.
> I've been trying to diagnose the issue, and I thought the problem was due to
> passing parameters between reports but it now appears this isn't the case.
> I have one report that has a subreport containing jumps to four other
> reports. 3 of the reports do not work, but one does. None of the reports
> require parameters to be passed, but the 3 that do not work have a parameter
> that requires selection before the report will be shown.
> If I place a default value in the report I'm jumping to, for the parameter
> being passed (in this case, an ID for the report) it works fine. So the
> issue appears to be when there is no default value for the parameter in the
> report I'm jumping to. Unfortunately, I can't just set a default value in
> this case.
> Has anyone come across this or know a workaround other than setting a
> default?
> Thanks again,
>
> Jon
>
> "Jonathan Martin" <jonathan.martin@.pcservicecall.co.uk> wrote in message
> news:%23SQ6CYsNFHA.3188@.TK2MSFTNGP10.phx.gbl...
> > Hi all,
> >
> > I'm having a problem with a series of reports I'm developing that allow
> > the user to design their own reports. They involve passing parameters
> > (and sometimes not passing parameters) between many different reports.
> > The issue I have is this:
> >
> > I have an opening page with no parameters. When I jump to the next report
> > (using Jump to Report in Properties -> Navigation tab) it begins to load
> > the next report, but the parameter bar is missing (not hidden) and the
> > report itself doesn't load (although the report title is displayed in the
> > top frame).
> >
> > If I use "Jump To URL", these issues appear to be less of a problem but
> > passing parameters is more difficult.
> >
> > A couple of questions for you:
> >
> > 1) Has anyone else experienced this issue?
> > 2) How can I pass parameters in a Jump to URL string, based on either
> > report parameters or report datasets?
> >
> > I've had a look around on the forums and have found some similar problems,
> > which is why I ended up looking at the Jump to URL option. I haven't
> > found anyone with the same issue though. Can anyone help?!
> >
> > Thanks in advance,
> >
> >
> > Jon
> >
>
>|||Unfortunately it's still causing issues with passing the parameter values.
It does work fine with passing the parameter through the URL though.
No idea why, but it's working!
Thanks for the help.
"jj#10" <jj10@.discussions.microsoft.com> wrote in message
news:DDB82610-A1B2-4518-AB28-20D55D6B4BEF@.microsoft.com...
> you have to set all parameters for the reports you are jumping to. This
> is
> easier with the "Jump to Report" option - just click the Parameters
> button.
> You can set hardcoded values are use other report items as input
> parameters.
> For URL jumps - use "?paramenter_name=parameter_value" after the URL
> address
> "Jonathan Martin" wrote:
>> A little more information for you.
>> I've been trying to diagnose the issue, and I thought the problem was due
>> to
>> passing parameters between reports but it now appears this isn't the
>> case.
>> I have one report that has a subreport containing jumps to four other
>> reports. 3 of the reports do not work, but one does. None of the
>> reports
>> require parameters to be passed, but the 3 that do not work have a
>> parameter
>> that requires selection before the report will be shown.
>> If I place a default value in the report I'm jumping to, for the
>> parameter
>> being passed (in this case, an ID for the report) it works fine. So the
>> issue appears to be when there is no default value for the parameter in
>> the
>> report I'm jumping to. Unfortunately, I can't just set a default value
>> in
>> this case.
>> Has anyone come across this or know a workaround other than setting a
>> default?
>> Thanks again,
>>
>> Jon
>>
>> "Jonathan Martin" <jonathan.martin@.pcservicecall.co.uk> wrote in message
>> news:%23SQ6CYsNFHA.3188@.TK2MSFTNGP10.phx.gbl...
>> > Hi all,
>> >
>> > I'm having a problem with a series of reports I'm developing that allow
>> > the user to design their own reports. They involve passing parameters
>> > (and sometimes not passing parameters) between many different reports.
>> > The issue I have is this:
>> >
>> > I have an opening page with no parameters. When I jump to the next
>> > report
>> > (using Jump to Report in Properties -> Navigation tab) it begins to
>> > load
>> > the next report, but the parameter bar is missing (not hidden) and the
>> > report itself doesn't load (although the report title is displayed in
>> > the
>> > top frame).
>> >
>> > If I use "Jump To URL", these issues appear to be less of a problem but
>> > passing parameters is more difficult.
>> >
>> > A couple of questions for you:
>> >
>> > 1) Has anyone else experienced this issue?
>> > 2) How can I pass parameters in a Jump to URL string, based on either
>> > report parameters or report datasets?
>> >
>> > I've had a look around on the forums and have found some similar
>> > problems,
>> > which is why I ended up looking at the Jump to URL option. I haven't
>> > found anyone with the same issue though. Can anyone help?!
>> >
>> > Thanks in advance,
>> >
>> >
>> > Jon
>> >
>>|||I am having a similar problem, but I use jump to report and it works fine in
development environment (i.e. visual studio), but does not work live.
"Jonathan Martin" wrote:
> Unfortunately it's still causing issues with passing the parameter values.
> It does work fine with passing the parameter through the URL though.
> No idea why, but it's working!
> Thanks for the help.
> "jj#10" <jj10@.discussions.microsoft.com> wrote in message
> news:DDB82610-A1B2-4518-AB28-20D55D6B4BEF@.microsoft.com...
> > you have to set all parameters for the reports you are jumping to. This
> > is
> > easier with the "Jump to Report" option - just click the Parameters
> > button.
> > You can set hardcoded values are use other report items as input
> > parameters.
> >
> > For URL jumps - use "?paramenter_name=parameter_value" after the URL
> > address
> >
> > "Jonathan Martin" wrote:
> >
> >> A little more information for you.
> >>
> >> I've been trying to diagnose the issue, and I thought the problem was due
> >> to
> >> passing parameters between reports but it now appears this isn't the
> >> case.
> >>
> >> I have one report that has a subreport containing jumps to four other
> >> reports. 3 of the reports do not work, but one does. None of the
> >> reports
> >> require parameters to be passed, but the 3 that do not work have a
> >> parameter
> >> that requires selection before the report will be shown.
> >>
> >> If I place a default value in the report I'm jumping to, for the
> >> parameter
> >> being passed (in this case, an ID for the report) it works fine. So the
> >> issue appears to be when there is no default value for the parameter in
> >> the
> >> report I'm jumping to. Unfortunately, I can't just set a default value
> >> in
> >> this case.
> >>
> >> Has anyone come across this or know a workaround other than setting a
> >> default?
> >>
> >> Thanks again,
> >>
> >>
> >> Jon
> >>
> >>
> >> "Jonathan Martin" <jonathan.martin@.pcservicecall.co.uk> wrote in message
> >> news:%23SQ6CYsNFHA.3188@.TK2MSFTNGP10.phx.gbl...
> >> > Hi all,
> >> >
> >> > I'm having a problem with a series of reports I'm developing that allow
> >> > the user to design their own reports. They involve passing parameters
> >> > (and sometimes not passing parameters) between many different reports.
> >> > The issue I have is this:
> >> >
> >> > I have an opening page with no parameters. When I jump to the next
> >> > report
> >> > (using Jump to Report in Properties -> Navigation tab) it begins to
> >> > load
> >> > the next report, but the parameter bar is missing (not hidden) and the
> >> > report itself doesn't load (although the report title is displayed in
> >> > the
> >> > top frame).
> >> >
> >> > If I use "Jump To URL", these issues appear to be less of a problem but
> >> > passing parameters is more difficult.
> >> >
> >> > A couple of questions for you:
> >> >
> >> > 1) Has anyone else experienced this issue?
> >> > 2) How can I pass parameters in a Jump to URL string, based on either
> >> > report parameters or report datasets?
> >> >
> >> > I've had a look around on the forums and have found some similar
> >> > problems,
> >> > which is why I ended up looking at the Jump to URL option. I haven't
> >> > found anyone with the same issue though. Can anyone help?!
> >> >
> >> > Thanks in advance,
> >> >
> >> >
> >> > Jon
> >> >
> >>
> >>
> >>
>
>|||Is the URL mapped to the correct "live" server (i.e. Not http://localhost/...)
Message posted via http://www.sqlmonster.com|||URL is mapped correctly and remember I am using "jump to report"
"Corey Crumbaugh via SQLMonster.com" wrote:
> Is the URL mapped to the correct "live" server (i.e. Not http://localhost/...)
>
> --
> Message posted via http://www.sqlmonster.com
>|||My guess is that the report in question (that you are jumping to) has a
credential problem. Can you run the report you are trying to jump to by
itself?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"bamboo" <bamboo@.discussions.microsoft.com> wrote in message
news:A1910C53-32D2-40D2-BB75-D67AF6779793@.microsoft.com...
> URL is mapped correctly and remember I am using "jump to report"
> "Corey Crumbaugh via SQLMonster.com" wrote:
>> Is the URL mapped to the correct "live" server (i.e. Not
>> http://localhost/...)
>>
>> --
>> Message posted via http://www.sqlmonster.com|||I found that the problem is the 2nd report has to be runnable right away
(i.e. cannot prompt user to enter parameters when it is being executed from
another report). This is not a good function.
Thus, this goes back to what jonathan posed.
"Bruce L-C [MVP]" wrote:
> My guess is that the report in question (that you are jumping to) has a
> credential problem. Can you run the report you are trying to jump to by
> itself?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "bamboo" <bamboo@.discussions.microsoft.com> wrote in message
> news:A1910C53-32D2-40D2-BB75-D67AF6779793@.microsoft.com...
> > URL is mapped correctly and remember I am using "jump to report"
> >
> > "Corey Crumbaugh via SQLMonster.com" wrote:
> >
> >> Is the URL mapped to the correct "live" server (i.e. Not
> >> http://localhost/...)
> >>
> >>
> >> --
> >> Message posted via http://www.sqlmonster.com
> >>
>
>
jump to report expression
Hello,
I have a field in my report that I want to jump to
another report but I want it to jump to different reports
depending on what is in that field. For example I click
the jump to report and put something like this in the
expression builder: Iif(Fields!Type = "a", ReportA,
ReportB) where ReportA and ReportB are two different
reports in my project. Can I do this? Everytime I try
to run it I get an error that says ReportA is not
defined. I can see it in the constants and just setting
the expression to ReportA jumps to that report. Thanks
for any help!please try IIF(Fields!Type = "a", "ReportA", "ReportB")
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Melissa" <anonymous@.discussions.microsoft.com> wrote in message
news:03eb01c49074$90d0ddf0$a401280a@.phx.gbl...
> Hello,
> I have a field in my report that I want to jump to
> another report but I want it to jump to different reports
> depending on what is in that field. For example I click
> the jump to report and put something like this in the
> expression builder: Iif(Fields!Type = "a", ReportA,
> ReportB) where ReportA and ReportB are two different
> reports in my project. Can I do this? Everytime I try
> to run it I get an error that says ReportA is not
> defined. I can see it in the constants and just setting
> the expression to ReportA jumps to that report. Thanks
> for any help!|||Cool Cool!! Thanks so much Lev.
>--Original Message--
>please try IIF(Fields!Type = "a", "ReportA", "ReportB")
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>"Melissa" <anonymous@.discussions.microsoft.com> wrote in
message
>news:03eb01c49074$90d0ddf0$a401280a@.phx.gbl...
>> Hello,
>> I have a field in my report that I want to jump to
>> another report but I want it to jump to different
reports
>> depending on what is in that field. For example I
click
>> the jump to report and put something like this in the
>> expression builder: Iif(Fields!Type = "a", ReportA,
>> ReportB) where ReportA and ReportB are two different
>> reports in my project. Can I do this? Everytime I try
>> to run it I get an error that says ReportA is not
>> defined. I can see it in the constants and just
setting
>> the expression to ReportA jumps to that report. Thanks
>> for any help!
>
>.
>
I have a field in my report that I want to jump to
another report but I want it to jump to different reports
depending on what is in that field. For example I click
the jump to report and put something like this in the
expression builder: Iif(Fields!Type = "a", ReportA,
ReportB) where ReportA and ReportB are two different
reports in my project. Can I do this? Everytime I try
to run it I get an error that says ReportA is not
defined. I can see it in the constants and just setting
the expression to ReportA jumps to that report. Thanks
for any help!please try IIF(Fields!Type = "a", "ReportA", "ReportB")
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Melissa" <anonymous@.discussions.microsoft.com> wrote in message
news:03eb01c49074$90d0ddf0$a401280a@.phx.gbl...
> Hello,
> I have a field in my report that I want to jump to
> another report but I want it to jump to different reports
> depending on what is in that field. For example I click
> the jump to report and put something like this in the
> expression builder: Iif(Fields!Type = "a", ReportA,
> ReportB) where ReportA and ReportB are two different
> reports in my project. Can I do this? Everytime I try
> to run it I get an error that says ReportA is not
> defined. I can see it in the constants and just setting
> the expression to ReportA jumps to that report. Thanks
> for any help!|||Cool Cool!! Thanks so much Lev.
>--Original Message--
>please try IIF(Fields!Type = "a", "ReportA", "ReportB")
>--
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>"Melissa" <anonymous@.discussions.microsoft.com> wrote in
message
>news:03eb01c49074$90d0ddf0$a401280a@.phx.gbl...
>> Hello,
>> I have a field in my report that I want to jump to
>> another report but I want it to jump to different
reports
>> depending on what is in that field. For example I
click
>> the jump to report and put something like this in the
>> expression builder: Iif(Fields!Type = "a", ReportA,
>> ReportB) where ReportA and ReportB are two different
>> reports in my project. Can I do this? Everytime I try
>> to run it I get an error that says ReportA is not
>> defined. I can see it in the constants and just
setting
>> the expression to ReportA jumps to that report. Thanks
>> for any help!
>
>.
>
Jump to Report - misdirection
I have created a baseline folder with several reports, which I use as a "link to" from production folders for a variety of departments. Moreover, I have used a "Jump To Report" configuration as a drill-through to another report. The problem is that when I click on the link it executes the report in the baseline folder versus the report in the production department folder. How do I direct the execution to the appropriate production department folder(s)? Thanks in advance for any assistance.
The link to the drillthrough report can either be relative to the current report, for ex:
detailsreport.rdl - which means we will look for it in the current folder, or
..\OtherFolder\detailsreport.rdl - relative to the path of the current report
or absolute:
/folder1/folder2/detailsreport.rdl - this path is relative to the report server root.
Either one of these can probably be made to work for your scenario.
Thanks
Tudor
|||I tried each option that you presented; however, I still don't get the results that I think should occur. I do, however, think we may be on the right track.
Let me restate the requirements a little differently. Let's say that I use the "Baseline" as the central storage area for all of my reports. Then, let's say I have two departments: Dept A and Dept B. Each department has its own separate folder with links to the same reports in Baseline; but, the parameters passed from each Department is somewhat different. For example, each would have a different department Id to distinquish itself.
Using this scenario and with the drill-through set as 'detailsreport.rdl', I would think that when executing the rdl from Dept A folder would use the detailsreport.rdl in Dept A folder. So far, this has not been the case for me. It executes the detailsreport.rdl in Baseline.
|||That is correct. If you use linked reports, the relative links will be relative to the reports that contain the definition, not the link.
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.
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
Jump to Bookmark in reports
Hi,
Please tell me how to implement the "Jump to Bookmark" in reports,
I mean to say, i have to move to another area or page in a report.
Please provide a sample for the same.
Thanks and Regards
Altaf Nizamuddin
Add bookmarks to connect the chart and the data matrix (optional). Enabling bookmark navigation from chart data points to the data matrix involves two steps. First, define the bookmark IDs within the data matrix. Second, define the jump to bookmark navigation action on the chart data point.
To add bookmarks in the data matrix, right-click the group header of the order year row group and select Properties from the context menu. In the Textbox Properties dialog box, select the Navigation tab and define the Bookmark ID expression by using an expression that generates a string:
=CStr(Fields!OrderYear.Value). This provides our bookmark jump targets.Open the Chart Properties dialog box and edit the data point properties. On the Action tab, select Jump to bookmark, and use the same expression as was used for the bookmark ID.
http://msdn2.microsoft.com/en-us/library/aa964128.aspx
sqlJump to a linked report
I have a problem using the jump-to feature in a linked report.
We are deploying all reports to a single folder 'Deployment' (not visible to
the browser role) and then creating links to these reports in folders that
are visible to the browser role. So from a maintenance point of view, there
is only ever one version of the report to update.
So we have report A that jumps-to report B and both of these are deployed to
the â'Deploymentâ' folder which is only visible to developers. We then create
links, AL and BL, to both A and B, in another folder called â'Runtimeâ' folder
which is visible to end users. End users are able to execute report AL fine
but when they try to jump-to BL, report manager looks for BL in the
â'Deploymentâ' folder instead of the â'Runtimeâ' folder, therefore, errors are
thrown because users donâ't have access to the â'Deployment Folderâ'.
How do we force the jump to action on linked reports to remain in the
current folder?
Obviously this seems to work fine if we are not using linked reports.
Hope this makes sense and any advice would be appreciated.
TIAWhat you want to be doing is doing a jump to the linked report, not the base
report. Instead of the name of the report (which assumes it is in the
current folder, i.e. Deployment folder in your case, do this instead:
/Runtime/TheReportYouWant
This will allow you to jump to the link report as you want. Note that it
means you have to deploy to test the link, you won't be able to test from
within Report Designer.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
>I have a problem using the jump-to feature in a linked report.
> We are deploying all reports to a single folder 'Deployment' (not visible
> to
> the browser role) and then creating links to these reports in folders that
> are visible to the browser role. So from a maintenance point of view,
> there
> is only ever one version of the report to update.
> So we have report A that jumps-to report B and both of these are deployed
> to
> the 'Deployment' folder which is only visible to developers. We then
> create
> links, AL and BL, to both A and B, in another folder called 'Runtime'
> folder
> which is visible to end users. End users are able to execute report AL
> fine
> but when they try to jump-to BL, report manager looks for BL in the
> 'Deployment' folder instead of the 'Runtime' folder, therefore, errors are
> thrown because users don't have access to the 'Deployment Folder'.
> How do we force the jump to action on linked reports to remain in the
> current folder?
> Obviously this seems to work fine if we are not using linked reports.
> Hope this makes sense and any advice would be appreciated.
> TIA
>|||Thanks Bruce.
But to further complicate matters...
If we only want to deploy one version of the main report, how would this
work if we wanted to have multiple links to the reports, i.e. one in
'Runtime' folder and one in 'Runtime2' folder, with different access
permissions on each folder?
Cheers
"Bruce L-C [MVP]" wrote:
> What you want to be doing is doing a jump to the linked report, not the base
> report. Instead of the name of the report (which assumes it is in the
> current folder, i.e. Deployment folder in your case, do this instead:
> /Runtime/TheReportYouWant
> This will allow you to jump to the link report as you want. Note that it
> means you have to deploy to test the link, you won't be able to test from
> within Report Designer.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> >I have a problem using the jump-to feature in a linked report.
> > We are deploying all reports to a single folder 'Deployment' (not visible
> > to
> > the browser role) and then creating links to these reports in folders that
> > are visible to the browser role. So from a maintenance point of view,
> > there
> > is only ever one version of the report to update.
> > So we have report A that jumps-to report B and both of these are deployed
> > to
> > the 'Deployment' folder which is only visible to developers. We then
> > create
> > links, AL and BL, to both A and B, in another folder called 'Runtime'
> > folder
> > which is visible to end users. End users are able to execute report AL
> > fine
> > but when they try to jump-to BL, report manager looks for BL in the
> > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors are
> > thrown because users don't have access to the 'Deployment Folder'.
> > How do we force the jump to action on linked reports to remain in the
> > current folder?
> > Obviously this seems to work fine if we are not using linked reports.
> > Hope this makes sense and any advice would be appreciated.
> > TIA
> >
>
>|||Do you realize that instead of all these links that you can set the report
permissions so that based on the role they only see the reports they have
rights to view?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
news:B108D0AF-8A60-4001-BA8D-99ACDC4A945E@.microsoft.com...
> Thanks Bruce.
> But to further complicate matters...
> If we only want to deploy one version of the main report, how would this
> work if we wanted to have multiple links to the reports, i.e. one in
> 'Runtime' folder and one in 'Runtime2' folder, with different access
> permissions on each folder?
> Cheers
> "Bruce L-C [MVP]" wrote:
>> What you want to be doing is doing a jump to the linked report, not the
>> base
>> report. Instead of the name of the report (which assumes it is in the
>> current folder, i.e. Deployment folder in your case, do this instead:
>> /Runtime/TheReportYouWant
>> This will allow you to jump to the link report as you want. Note that it
>> means you have to deploy to test the link, you won't be able to test from
>> within Report Designer.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
>> >I have a problem using the jump-to feature in a linked report.
>> > We are deploying all reports to a single folder 'Deployment' (not
>> > visible
>> > to
>> > the browser role) and then creating links to these reports in folders
>> > that
>> > are visible to the browser role. So from a maintenance point of view,
>> > there
>> > is only ever one version of the report to update.
>> > So we have report A that jumps-to report B and both of these are
>> > deployed
>> > to
>> > the 'Deployment' folder which is only visible to developers. We then
>> > create
>> > links, AL and BL, to both A and B, in another folder called 'Runtime'
>> > folder
>> > which is visible to end users. End users are able to execute report AL
>> > fine
>> > but when they try to jump-to BL, report manager looks for BL in the
>> > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors
>> > are
>> > thrown because users don't have access to the 'Deployment Folder'.
>> > How do we force the jump to action on linked reports to remain in the
>> > current folder?
>> > Obviously this seems to work fine if we are not using linked reports.
>> > Hope this makes sense and any advice would be appreciated.
>> > TIA
>> >
>>|||I guess we can but we need to be able to specify different parameters for
each report depending on who is viewing it.
Does that make sense or do you think we are going about things in the wrong
way?
"Bruce L-C [MVP]" wrote:
> Do you realize that instead of all these links that you can set the report
> permissions so that based on the role they only see the reports they have
> rights to view?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> news:B108D0AF-8A60-4001-BA8D-99ACDC4A945E@.microsoft.com...
> > Thanks Bruce.
> >
> > But to further complicate matters...
> >
> > If we only want to deploy one version of the main report, how would this
> > work if we wanted to have multiple links to the reports, i.e. one in
> > 'Runtime' folder and one in 'Runtime2' folder, with different access
> > permissions on each folder?
> >
> > Cheers
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> What you want to be doing is doing a jump to the linked report, not the
> >> base
> >> report. Instead of the name of the report (which assumes it is in the
> >> current folder, i.e. Deployment folder in your case, do this instead:
> >>
> >> /Runtime/TheReportYouWant
> >>
> >> This will allow you to jump to the link report as you want. Note that it
> >> means you have to deploy to test the link, you won't be able to test from
> >> within Report Designer.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> >> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> >> >I have a problem using the jump-to feature in a linked report.
> >> > We are deploying all reports to a single folder 'Deployment' (not
> >> > visible
> >> > to
> >> > the browser role) and then creating links to these reports in folders
> >> > that
> >> > are visible to the browser role. So from a maintenance point of view,
> >> > there
> >> > is only ever one version of the report to update.
> >> > So we have report A that jumps-to report B and both of these are
> >> > deployed
> >> > to
> >> > the 'Deployment' folder which is only visible to developers. We then
> >> > create
> >> > links, AL and BL, to both A and B, in another folder called 'Runtime'
> >> > folder
> >> > which is visible to end users. End users are able to execute report AL
> >> > fine
> >> > but when they try to jump-to BL, report manager looks for BL in the
> >> > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors
> >> > are
> >> > thrown because users don't have access to the 'Deployment Folder'.
> >> > How do we force the jump to action on linked reports to remain in the
> >> > current folder?
> >> > Obviously this seems to work fine if we are not using linked reports.
> >> > Hope this makes sense and any advice would be appreciated.
> >> > TIA
> >> >
> >>
> >>
> >>
>
>|||Is the user going to this or are you integrating into your own app. It
sounds like here you are integrating it into your app.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
news:8B07B2C4-34CA-461B-929F-6DBEB4B44AAC@.microsoft.com...
>I guess we can but we need to be able to specify different parameters for
> each report depending on who is viewing it.
> Does that make sense or do you think we are going about things in the
> wrong
> way?
> "Bruce L-C [MVP]" wrote:
>> Do you realize that instead of all these links that you can set the
>> report
>> permissions so that based on the role they only see the reports they have
>> rights to view?
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> news:B108D0AF-8A60-4001-BA8D-99ACDC4A945E@.microsoft.com...
>> > Thanks Bruce.
>> >
>> > But to further complicate matters...
>> >
>> > If we only want to deploy one version of the main report, how would
>> > this
>> > work if we wanted to have multiple links to the reports, i.e. one in
>> > 'Runtime' folder and one in 'Runtime2' folder, with different access
>> > permissions on each folder?
>> >
>> > Cheers
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> What you want to be doing is doing a jump to the linked report, not
>> >> the
>> >> base
>> >> report. Instead of the name of the report (which assumes it is in the
>> >> current folder, i.e. Deployment folder in your case, do this instead:
>> >>
>> >> /Runtime/TheReportYouWant
>> >>
>> >> This will allow you to jump to the link report as you want. Note that
>> >> it
>> >> means you have to deploy to test the link, you won't be able to test
>> >> from
>> >> within Report Designer.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> >> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
>> >> >I have a problem using the jump-to feature in a linked report.
>> >> > We are deploying all reports to a single folder 'Deployment' (not
>> >> > visible
>> >> > to
>> >> > the browser role) and then creating links to these reports in
>> >> > folders
>> >> > that
>> >> > are visible to the browser role. So from a maintenance point of
>> >> > view,
>> >> > there
>> >> > is only ever one version of the report to update.
>> >> > So we have report A that jumps-to report B and both of these are
>> >> > deployed
>> >> > to
>> >> > the 'Deployment' folder which is only visible to developers. We
>> >> > then
>> >> > create
>> >> > links, AL and BL, to both A and B, in another folder called
>> >> > 'Runtime'
>> >> > folder
>> >> > which is visible to end users. End users are able to execute report
>> >> > AL
>> >> > fine
>> >> > but when they try to jump-to BL, report manager looks for BL in the
>> >> > 'Deployment' folder instead of the 'Runtime' folder, therefore,
>> >> > errors
>> >> > are
>> >> > thrown because users don't have access to the 'Deployment Folder'.
>> >> > How do we force the jump to action on linked reports to remain in
>> >> > the
>> >> > current folder?
>> >> > Obviously this seems to work fine if we are not using linked
>> >> > reports.
>> >> > Hope this makes sense and any advice would be appreciated.
>> >> > TIA
>> >> >
>> >>
>> >>
>> >>
>>|||Both really, but primarily users will access the reports directly through
report manager.
"Bruce L-C [MVP]" wrote:
> Is the user going to this or are you integrating into your own app. It
> sounds like here you are integrating it into your app.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> news:8B07B2C4-34CA-461B-929F-6DBEB4B44AAC@.microsoft.com...
> >I guess we can but we need to be able to specify different parameters for
> > each report depending on who is viewing it.
> >
> > Does that make sense or do you think we are going about things in the
> > wrong
> > way?
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Do you realize that instead of all these links that you can set the
> >> report
> >> permissions so that based on the role they only see the reports they have
> >> rights to view?
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> >> news:B108D0AF-8A60-4001-BA8D-99ACDC4A945E@.microsoft.com...
> >> > Thanks Bruce.
> >> >
> >> > But to further complicate matters...
> >> >
> >> > If we only want to deploy one version of the main report, how would
> >> > this
> >> > work if we wanted to have multiple links to the reports, i.e. one in
> >> > 'Runtime' folder and one in 'Runtime2' folder, with different access
> >> > permissions on each folder?
> >> >
> >> > Cheers
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> What you want to be doing is doing a jump to the linked report, not
> >> >> the
> >> >> base
> >> >> report. Instead of the name of the report (which assumes it is in the
> >> >> current folder, i.e. Deployment folder in your case, do this instead:
> >> >>
> >> >> /Runtime/TheReportYouWant
> >> >>
> >> >> This will allow you to jump to the link report as you want. Note that
> >> >> it
> >> >> means you have to deploy to test the link, you won't be able to test
> >> >> from
> >> >> within Report Designer.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> >> >> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> >> >> >I have a problem using the jump-to feature in a linked report.
> >> >> > We are deploying all reports to a single folder 'Deployment' (not
> >> >> > visible
> >> >> > to
> >> >> > the browser role) and then creating links to these reports in
> >> >> > folders
> >> >> > that
> >> >> > are visible to the browser role. So from a maintenance point of
> >> >> > view,
> >> >> > there
> >> >> > is only ever one version of the report to update.
> >> >> > So we have report A that jumps-to report B and both of these are
> >> >> > deployed
> >> >> > to
> >> >> > the 'Deployment' folder which is only visible to developers. We
> >> >> > then
> >> >> > create
> >> >> > links, AL and BL, to both A and B, in another folder called
> >> >> > 'Runtime'
> >> >> > folder
> >> >> > which is visible to end users. End users are able to execute report
> >> >> > AL
> >> >> > fine
> >> >> > but when they try to jump-to BL, report manager looks for BL in the
> >> >> > 'Deployment' folder instead of the 'Runtime' folder, therefore,
> >> >> > errors
> >> >> > are
> >> >> > thrown because users don't have access to the 'Deployment Folder'.
> >> >> > How do we force the jump to action on linked reports to remain in
> >> >> > the
> >> >> > current folder?
> >> >> > Obviously this seems to work fine if we are not using linked
> >> >> > reports.
> >> >> > Hope this makes sense and any advice would be appreciated.
> >> >> > TIA
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||One thing you can do is use the global variable User!UserID. Then query a
table that holds the report configuration options in a table. Query
parameters do not have to map to report parameters.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
news:620FB6AB-309D-4B45-85F7-296867EBD074@.microsoft.com...
> Both really, but primarily users will access the reports directly through
> report manager.
> "Bruce L-C [MVP]" wrote:
>> Is the user going to this or are you integrating into your own app. It
>> sounds like here you are integrating it into your app.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> news:8B07B2C4-34CA-461B-929F-6DBEB4B44AAC@.microsoft.com...
>> >I guess we can but we need to be able to specify different parameters
>> >for
>> > each report depending on who is viewing it.
>> >
>> > Does that make sense or do you think we are going about things in the
>> > wrong
>> > way?
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Do you realize that instead of all these links that you can set the
>> >> report
>> >> permissions so that based on the role they only see the reports they
>> >> have
>> >> rights to view?
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> >> news:B108D0AF-8A60-4001-BA8D-99ACDC4A945E@.microsoft.com...
>> >> > Thanks Bruce.
>> >> >
>> >> > But to further complicate matters...
>> >> >
>> >> > If we only want to deploy one version of the main report, how would
>> >> > this
>> >> > work if we wanted to have multiple links to the reports, i.e. one in
>> >> > 'Runtime' folder and one in 'Runtime2' folder, with different access
>> >> > permissions on each folder?
>> >> >
>> >> > Cheers
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> What you want to be doing is doing a jump to the linked report, not
>> >> >> the
>> >> >> base
>> >> >> report. Instead of the name of the report (which assumes it is in
>> >> >> the
>> >> >> current folder, i.e. Deployment folder in your case, do this
>> >> >> instead:
>> >> >>
>> >> >> /Runtime/TheReportYouWant
>> >> >>
>> >> >> This will allow you to jump to the link report as you want. Note
>> >> >> that
>> >> >> it
>> >> >> means you have to deploy to test the link, you won't be able to
>> >> >> test
>> >> >> from
>> >> >> within Report Designer.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> >> >> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
>> >> >> >I have a problem using the jump-to feature in a linked report.
>> >> >> > We are deploying all reports to a single folder 'Deployment' (not
>> >> >> > visible
>> >> >> > to
>> >> >> > the browser role) and then creating links to these reports in
>> >> >> > folders
>> >> >> > that
>> >> >> > are visible to the browser role. So from a maintenance point of
>> >> >> > view,
>> >> >> > there
>> >> >> > is only ever one version of the report to update.
>> >> >> > So we have report A that jumps-to report B and both of these are
>> >> >> > deployed
>> >> >> > to
>> >> >> > the 'Deployment' folder which is only visible to developers. We
>> >> >> > then
>> >> >> > create
>> >> >> > links, AL and BL, to both A and B, in another folder called
>> >> >> > 'Runtime'
>> >> >> > folder
>> >> >> > which is visible to end users. End users are able to execute
>> >> >> > report
>> >> >> > AL
>> >> >> > fine
>> >> >> > but when they try to jump-to BL, report manager looks for BL in
>> >> >> > the
>> >> >> > 'Deployment' folder instead of the 'Runtime' folder, therefore,
>> >> >> > errors
>> >> >> > are
>> >> >> > thrown because users don't have access to the 'Deployment
>> >> >> > Folder'.
>> >> >> > How do we force the jump to action on linked reports to remain in
>> >> >> > the
>> >> >> > current folder?
>> >> >> > Obviously this seems to work fine if we are not using linked
>> >> >> > reports.
>> >> >> > Hope this makes sense and any advice would be appreciated.
>> >> >> > TIA
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||I have an identical Management requirement (meaning the higher levels of
management have decided to do this, and told me to figure out how).
Like trmpalmer, I published all me report to a "Production Reports" folder,
hidden from browsers. Like trmpalmer, I have been instructed to create
various folders based on management dictated groups, which will also be
duplicated in ADS to give specific groups access to specific reports
designated for that group/department.
Also like trmpalmer, some of my reports use Jump-To to reach other reports.
I tried relative pathing, i.e. " ./Report_2_Name " but that didn't help.
Linked Reports is ideal for me becasue of the administration issue of
maintaining multiple copies of the same report, versus maintaining a single
report and linking to that master copy. I am really hopng to find a solution
that will allow me to use Linked Reports and Jump-To-Report at the same time.
"trmpalmer" wrote:
> Thanks Bruce.
> But to further complicate matters...
> If we only want to deploy one version of the main report, how would this
> work if we wanted to have multiple links to the reports, i.e. one in
> 'Runtime' folder and one in 'Runtime2' folder, with different access
> permissions on each folder?
> Cheers
> "Bruce L-C [MVP]" wrote:
> > What you want to be doing is doing a jump to the linked report, not the base
> > report. Instead of the name of the report (which assumes it is in the
> > current folder, i.e. Deployment folder in your case, do this instead:
> >
> > /Runtime/TheReportYouWant
> >
> > This will allow you to jump to the link report as you want. Note that it
> > means you have to deploy to test the link, you won't be able to test from
> > within Report Designer.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> > news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> > >I have a problem using the jump-to feature in a linked report.
> > > We are deploying all reports to a single folder 'Deployment' (not visible
> > > to
> > > the browser role) and then creating links to these reports in folders that
> > > are visible to the browser role. So from a maintenance point of view,
> > > there
> > > is only ever one version of the report to update.
> > > So we have report A that jumps-to report B and both of these are deployed
> > > to
> > > the 'Deployment' folder which is only visible to developers. We then
> > > create
> > > links, AL and BL, to both A and B, in another folder called 'Runtime'
> > > folder
> > > which is visible to end users. End users are able to execute report AL
> > > fine
> > > but when they try to jump-to BL, report manager looks for BL in the
> > > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors are
> > > thrown because users don't have access to the 'Deployment Folder'.
> > > How do we force the jump to action on linked reports to remain in the
> > > current folder?
> > > Obviously this seems to work fine if we are not using linked reports.
> > > Hope this makes sense and any advice would be appreciated.
> > > TIA
> > >
> >
> >
> >|||I just found a solution, and I wanted to share it here, and I will make a
seperate post.
To accomplish the goal of having a Linked Report perform a Jump-To with a
target report within the same directory as the initial linked report (the
target can also be a linked report), you need some means of "relative
pathing". This can be achieved with the following placed in the Jump to
Report field (click on the fx button or type directly):
=Globals!ReportFolder + "/" + "ReportName"
This will grab the folder the report being run is in. So if you have a
report in runtime2, it would show "/runtime2/ReportName", but would show
"/runtime/ReportName" when run from the runtime folder.
"trmpalmer" wrote:
> Thanks Bruce.
> But to further complicate matters...
> If we only want to deploy one version of the main report, how would this
> work if we wanted to have multiple links to the reports, i.e. one in
> 'Runtime' folder and one in 'Runtime2' folder, with different access
> permissions on each folder?
> Cheers
> "Bruce L-C [MVP]" wrote:
> > What you want to be doing is doing a jump to the linked report, not the base
> > report. Instead of the name of the report (which assumes it is in the
> > current folder, i.e. Deployment folder in your case, do this instead:
> >
> > /Runtime/TheReportYouWant
> >
> > This will allow you to jump to the link report as you want. Note that it
> > means you have to deploy to test the link, you won't be able to test from
> > within Report Designer.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> > news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> > >I have a problem using the jump-to feature in a linked report.
> > > We are deploying all reports to a single folder 'Deployment' (not visible
> > > to
> > > the browser role) and then creating links to these reports in folders that
> > > are visible to the browser role. So from a maintenance point of view,
> > > there
> > > is only ever one version of the report to update.
> > > So we have report A that jumps-to report B and both of these are deployed
> > > to
> > > the 'Deployment' folder which is only visible to developers. We then
> > > create
> > > links, AL and BL, to both A and B, in another folder called 'Runtime'
> > > folder
> > > which is visible to end users. End users are able to execute report AL
> > > fine
> > > but when they try to jump-to BL, report manager looks for BL in the
> > > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors are
> > > thrown because users don't have access to the 'Deployment Folder'.
> > > How do we force the jump to action on linked reports to remain in the
> > > current folder?
> > > Obviously this seems to work fine if we are not using linked reports.
> > > Hope this makes sense and any advice would be appreciated.
> > > TIA
> > >
> >
> >
> >|||Thanks a million!!
Just what I was looking for :-)
"Rob 'Spike' Stevens" wrote:
> I just found a solution, and I wanted to share it here, and I will make a
> seperate post.
> To accomplish the goal of having a Linked Report perform a Jump-To with a
> target report within the same directory as the initial linked report (the
> target can also be a linked report), you need some means of "relative
> pathing". This can be achieved with the following placed in the Jump to
> Report field (click on the fx button or type directly):
> =Globals!ReportFolder + "/" + "ReportName"
> This will grab the folder the report being run is in. So if you have a
> report in runtime2, it would show "/runtime2/ReportName", but would show
> "/runtime/ReportName" when run from the runtime folder.
> "trmpalmer" wrote:
> > Thanks Bruce.
> >
> > But to further complicate matters...
> >
> > If we only want to deploy one version of the main report, how would this
> > work if we wanted to have multiple links to the reports, i.e. one in
> > 'Runtime' folder and one in 'Runtime2' folder, with different access
> > permissions on each folder?
> >
> > Cheers
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > What you want to be doing is doing a jump to the linked report, not the base
> > > report. Instead of the name of the report (which assumes it is in the
> > > current folder, i.e. Deployment folder in your case, do this instead:
> > >
> > > /Runtime/TheReportYouWant
> > >
> > > This will allow you to jump to the link report as you want. Note that it
> > > means you have to deploy to test the link, you won't be able to test from
> > > within Report Designer.
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> > > news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> > > >I have a problem using the jump-to feature in a linked report.
> > > > We are deploying all reports to a single folder 'Deployment' (not visible
> > > > to
> > > > the browser role) and then creating links to these reports in folders that
> > > > are visible to the browser role. So from a maintenance point of view,
> > > > there
> > > > is only ever one version of the report to update.
> > > > So we have report A that jumps-to report B and both of these are deployed
> > > > to
> > > > the 'Deployment' folder which is only visible to developers. We then
> > > > create
> > > > links, AL and BL, to both A and B, in another folder called 'Runtime'
> > > > folder
> > > > which is visible to end users. End users are able to execute report AL
> > > > fine
> > > > but when they try to jump-to BL, report manager looks for BL in the
> > > > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors are
> > > > thrown because users don't have access to the 'Deployment Folder'.
> > > > How do we force the jump to action on linked reports to remain in the
> > > > current folder?
> > > > Obviously this seems to work fine if we are not using linked reports.
> > > > Hope this makes sense and any advice would be appreciated.
> > > > TIA
> > > >
> > >
> > >
> > >
We are deploying all reports to a single folder 'Deployment' (not visible to
the browser role) and then creating links to these reports in folders that
are visible to the browser role. So from a maintenance point of view, there
is only ever one version of the report to update.
So we have report A that jumps-to report B and both of these are deployed to
the â'Deploymentâ' folder which is only visible to developers. We then create
links, AL and BL, to both A and B, in another folder called â'Runtimeâ' folder
which is visible to end users. End users are able to execute report AL fine
but when they try to jump-to BL, report manager looks for BL in the
â'Deploymentâ' folder instead of the â'Runtimeâ' folder, therefore, errors are
thrown because users donâ't have access to the â'Deployment Folderâ'.
How do we force the jump to action on linked reports to remain in the
current folder?
Obviously this seems to work fine if we are not using linked reports.
Hope this makes sense and any advice would be appreciated.
TIAWhat you want to be doing is doing a jump to the linked report, not the base
report. Instead of the name of the report (which assumes it is in the
current folder, i.e. Deployment folder in your case, do this instead:
/Runtime/TheReportYouWant
This will allow you to jump to the link report as you want. Note that it
means you have to deploy to test the link, you won't be able to test from
within Report Designer.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
>I have a problem using the jump-to feature in a linked report.
> We are deploying all reports to a single folder 'Deployment' (not visible
> to
> the browser role) and then creating links to these reports in folders that
> are visible to the browser role. So from a maintenance point of view,
> there
> is only ever one version of the report to update.
> So we have report A that jumps-to report B and both of these are deployed
> to
> the 'Deployment' folder which is only visible to developers. We then
> create
> links, AL and BL, to both A and B, in another folder called 'Runtime'
> folder
> which is visible to end users. End users are able to execute report AL
> fine
> but when they try to jump-to BL, report manager looks for BL in the
> 'Deployment' folder instead of the 'Runtime' folder, therefore, errors are
> thrown because users don't have access to the 'Deployment Folder'.
> How do we force the jump to action on linked reports to remain in the
> current folder?
> Obviously this seems to work fine if we are not using linked reports.
> Hope this makes sense and any advice would be appreciated.
> TIA
>|||Thanks Bruce.
But to further complicate matters...
If we only want to deploy one version of the main report, how would this
work if we wanted to have multiple links to the reports, i.e. one in
'Runtime' folder and one in 'Runtime2' folder, with different access
permissions on each folder?
Cheers
"Bruce L-C [MVP]" wrote:
> What you want to be doing is doing a jump to the linked report, not the base
> report. Instead of the name of the report (which assumes it is in the
> current folder, i.e. Deployment folder in your case, do this instead:
> /Runtime/TheReportYouWant
> This will allow you to jump to the link report as you want. Note that it
> means you have to deploy to test the link, you won't be able to test from
> within Report Designer.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> >I have a problem using the jump-to feature in a linked report.
> > We are deploying all reports to a single folder 'Deployment' (not visible
> > to
> > the browser role) and then creating links to these reports in folders that
> > are visible to the browser role. So from a maintenance point of view,
> > there
> > is only ever one version of the report to update.
> > So we have report A that jumps-to report B and both of these are deployed
> > to
> > the 'Deployment' folder which is only visible to developers. We then
> > create
> > links, AL and BL, to both A and B, in another folder called 'Runtime'
> > folder
> > which is visible to end users. End users are able to execute report AL
> > fine
> > but when they try to jump-to BL, report manager looks for BL in the
> > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors are
> > thrown because users don't have access to the 'Deployment Folder'.
> > How do we force the jump to action on linked reports to remain in the
> > current folder?
> > Obviously this seems to work fine if we are not using linked reports.
> > Hope this makes sense and any advice would be appreciated.
> > TIA
> >
>
>|||Do you realize that instead of all these links that you can set the report
permissions so that based on the role they only see the reports they have
rights to view?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
news:B108D0AF-8A60-4001-BA8D-99ACDC4A945E@.microsoft.com...
> Thanks Bruce.
> But to further complicate matters...
> If we only want to deploy one version of the main report, how would this
> work if we wanted to have multiple links to the reports, i.e. one in
> 'Runtime' folder and one in 'Runtime2' folder, with different access
> permissions on each folder?
> Cheers
> "Bruce L-C [MVP]" wrote:
>> What you want to be doing is doing a jump to the linked report, not the
>> base
>> report. Instead of the name of the report (which assumes it is in the
>> current folder, i.e. Deployment folder in your case, do this instead:
>> /Runtime/TheReportYouWant
>> This will allow you to jump to the link report as you want. Note that it
>> means you have to deploy to test the link, you won't be able to test from
>> within Report Designer.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
>> >I have a problem using the jump-to feature in a linked report.
>> > We are deploying all reports to a single folder 'Deployment' (not
>> > visible
>> > to
>> > the browser role) and then creating links to these reports in folders
>> > that
>> > are visible to the browser role. So from a maintenance point of view,
>> > there
>> > is only ever one version of the report to update.
>> > So we have report A that jumps-to report B and both of these are
>> > deployed
>> > to
>> > the 'Deployment' folder which is only visible to developers. We then
>> > create
>> > links, AL and BL, to both A and B, in another folder called 'Runtime'
>> > folder
>> > which is visible to end users. End users are able to execute report AL
>> > fine
>> > but when they try to jump-to BL, report manager looks for BL in the
>> > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors
>> > are
>> > thrown because users don't have access to the 'Deployment Folder'.
>> > How do we force the jump to action on linked reports to remain in the
>> > current folder?
>> > Obviously this seems to work fine if we are not using linked reports.
>> > Hope this makes sense and any advice would be appreciated.
>> > TIA
>> >
>>|||I guess we can but we need to be able to specify different parameters for
each report depending on who is viewing it.
Does that make sense or do you think we are going about things in the wrong
way?
"Bruce L-C [MVP]" wrote:
> Do you realize that instead of all these links that you can set the report
> permissions so that based on the role they only see the reports they have
> rights to view?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> news:B108D0AF-8A60-4001-BA8D-99ACDC4A945E@.microsoft.com...
> > Thanks Bruce.
> >
> > But to further complicate matters...
> >
> > If we only want to deploy one version of the main report, how would this
> > work if we wanted to have multiple links to the reports, i.e. one in
> > 'Runtime' folder and one in 'Runtime2' folder, with different access
> > permissions on each folder?
> >
> > Cheers
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> What you want to be doing is doing a jump to the linked report, not the
> >> base
> >> report. Instead of the name of the report (which assumes it is in the
> >> current folder, i.e. Deployment folder in your case, do this instead:
> >>
> >> /Runtime/TheReportYouWant
> >>
> >> This will allow you to jump to the link report as you want. Note that it
> >> means you have to deploy to test the link, you won't be able to test from
> >> within Report Designer.
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> >> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> >> >I have a problem using the jump-to feature in a linked report.
> >> > We are deploying all reports to a single folder 'Deployment' (not
> >> > visible
> >> > to
> >> > the browser role) and then creating links to these reports in folders
> >> > that
> >> > are visible to the browser role. So from a maintenance point of view,
> >> > there
> >> > is only ever one version of the report to update.
> >> > So we have report A that jumps-to report B and both of these are
> >> > deployed
> >> > to
> >> > the 'Deployment' folder which is only visible to developers. We then
> >> > create
> >> > links, AL and BL, to both A and B, in another folder called 'Runtime'
> >> > folder
> >> > which is visible to end users. End users are able to execute report AL
> >> > fine
> >> > but when they try to jump-to BL, report manager looks for BL in the
> >> > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors
> >> > are
> >> > thrown because users don't have access to the 'Deployment Folder'.
> >> > How do we force the jump to action on linked reports to remain in the
> >> > current folder?
> >> > Obviously this seems to work fine if we are not using linked reports.
> >> > Hope this makes sense and any advice would be appreciated.
> >> > TIA
> >> >
> >>
> >>
> >>
>
>|||Is the user going to this or are you integrating into your own app. It
sounds like here you are integrating it into your app.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
news:8B07B2C4-34CA-461B-929F-6DBEB4B44AAC@.microsoft.com...
>I guess we can but we need to be able to specify different parameters for
> each report depending on who is viewing it.
> Does that make sense or do you think we are going about things in the
> wrong
> way?
> "Bruce L-C [MVP]" wrote:
>> Do you realize that instead of all these links that you can set the
>> report
>> permissions so that based on the role they only see the reports they have
>> rights to view?
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> news:B108D0AF-8A60-4001-BA8D-99ACDC4A945E@.microsoft.com...
>> > Thanks Bruce.
>> >
>> > But to further complicate matters...
>> >
>> > If we only want to deploy one version of the main report, how would
>> > this
>> > work if we wanted to have multiple links to the reports, i.e. one in
>> > 'Runtime' folder and one in 'Runtime2' folder, with different access
>> > permissions on each folder?
>> >
>> > Cheers
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> What you want to be doing is doing a jump to the linked report, not
>> >> the
>> >> base
>> >> report. Instead of the name of the report (which assumes it is in the
>> >> current folder, i.e. Deployment folder in your case, do this instead:
>> >>
>> >> /Runtime/TheReportYouWant
>> >>
>> >> This will allow you to jump to the link report as you want. Note that
>> >> it
>> >> means you have to deploy to test the link, you won't be able to test
>> >> from
>> >> within Report Designer.
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> >> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
>> >> >I have a problem using the jump-to feature in a linked report.
>> >> > We are deploying all reports to a single folder 'Deployment' (not
>> >> > visible
>> >> > to
>> >> > the browser role) and then creating links to these reports in
>> >> > folders
>> >> > that
>> >> > are visible to the browser role. So from a maintenance point of
>> >> > view,
>> >> > there
>> >> > is only ever one version of the report to update.
>> >> > So we have report A that jumps-to report B and both of these are
>> >> > deployed
>> >> > to
>> >> > the 'Deployment' folder which is only visible to developers. We
>> >> > then
>> >> > create
>> >> > links, AL and BL, to both A and B, in another folder called
>> >> > 'Runtime'
>> >> > folder
>> >> > which is visible to end users. End users are able to execute report
>> >> > AL
>> >> > fine
>> >> > but when they try to jump-to BL, report manager looks for BL in the
>> >> > 'Deployment' folder instead of the 'Runtime' folder, therefore,
>> >> > errors
>> >> > are
>> >> > thrown because users don't have access to the 'Deployment Folder'.
>> >> > How do we force the jump to action on linked reports to remain in
>> >> > the
>> >> > current folder?
>> >> > Obviously this seems to work fine if we are not using linked
>> >> > reports.
>> >> > Hope this makes sense and any advice would be appreciated.
>> >> > TIA
>> >> >
>> >>
>> >>
>> >>
>>|||Both really, but primarily users will access the reports directly through
report manager.
"Bruce L-C [MVP]" wrote:
> Is the user going to this or are you integrating into your own app. It
> sounds like here you are integrating it into your app.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> news:8B07B2C4-34CA-461B-929F-6DBEB4B44AAC@.microsoft.com...
> >I guess we can but we need to be able to specify different parameters for
> > each report depending on who is viewing it.
> >
> > Does that make sense or do you think we are going about things in the
> > wrong
> > way?
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> Do you realize that instead of all these links that you can set the
> >> report
> >> permissions so that based on the role they only see the reports they have
> >> rights to view?
> >>
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> >> news:B108D0AF-8A60-4001-BA8D-99ACDC4A945E@.microsoft.com...
> >> > Thanks Bruce.
> >> >
> >> > But to further complicate matters...
> >> >
> >> > If we only want to deploy one version of the main report, how would
> >> > this
> >> > work if we wanted to have multiple links to the reports, i.e. one in
> >> > 'Runtime' folder and one in 'Runtime2' folder, with different access
> >> > permissions on each folder?
> >> >
> >> > Cheers
> >> >
> >> > "Bruce L-C [MVP]" wrote:
> >> >
> >> >> What you want to be doing is doing a jump to the linked report, not
> >> >> the
> >> >> base
> >> >> report. Instead of the name of the report (which assumes it is in the
> >> >> current folder, i.e. Deployment folder in your case, do this instead:
> >> >>
> >> >> /Runtime/TheReportYouWant
> >> >>
> >> >> This will allow you to jump to the link report as you want. Note that
> >> >> it
> >> >> means you have to deploy to test the link, you won't be able to test
> >> >> from
> >> >> within Report Designer.
> >> >>
> >> >>
> >> >> --
> >> >> Bruce Loehle-Conger
> >> >> MVP SQL Server Reporting Services
> >> >>
> >> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> >> >> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> >> >> >I have a problem using the jump-to feature in a linked report.
> >> >> > We are deploying all reports to a single folder 'Deployment' (not
> >> >> > visible
> >> >> > to
> >> >> > the browser role) and then creating links to these reports in
> >> >> > folders
> >> >> > that
> >> >> > are visible to the browser role. So from a maintenance point of
> >> >> > view,
> >> >> > there
> >> >> > is only ever one version of the report to update.
> >> >> > So we have report A that jumps-to report B and both of these are
> >> >> > deployed
> >> >> > to
> >> >> > the 'Deployment' folder which is only visible to developers. We
> >> >> > then
> >> >> > create
> >> >> > links, AL and BL, to both A and B, in another folder called
> >> >> > 'Runtime'
> >> >> > folder
> >> >> > which is visible to end users. End users are able to execute report
> >> >> > AL
> >> >> > fine
> >> >> > but when they try to jump-to BL, report manager looks for BL in the
> >> >> > 'Deployment' folder instead of the 'Runtime' folder, therefore,
> >> >> > errors
> >> >> > are
> >> >> > thrown because users don't have access to the 'Deployment Folder'.
> >> >> > How do we force the jump to action on linked reports to remain in
> >> >> > the
> >> >> > current folder?
> >> >> > Obviously this seems to work fine if we are not using linked
> >> >> > reports.
> >> >> > Hope this makes sense and any advice would be appreciated.
> >> >> > TIA
> >> >> >
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>|||One thing you can do is use the global variable User!UserID. Then query a
table that holds the report configuration options in a table. Query
parameters do not have to map to report parameters.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
news:620FB6AB-309D-4B45-85F7-296867EBD074@.microsoft.com...
> Both really, but primarily users will access the reports directly through
> report manager.
> "Bruce L-C [MVP]" wrote:
>> Is the user going to this or are you integrating into your own app. It
>> sounds like here you are integrating it into your app.
>>
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>>
>> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> news:8B07B2C4-34CA-461B-929F-6DBEB4B44AAC@.microsoft.com...
>> >I guess we can but we need to be able to specify different parameters
>> >for
>> > each report depending on who is viewing it.
>> >
>> > Does that make sense or do you think we are going about things in the
>> > wrong
>> > way?
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> Do you realize that instead of all these links that you can set the
>> >> report
>> >> permissions so that based on the role they only see the reports they
>> >> have
>> >> rights to view?
>> >>
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> >> news:B108D0AF-8A60-4001-BA8D-99ACDC4A945E@.microsoft.com...
>> >> > Thanks Bruce.
>> >> >
>> >> > But to further complicate matters...
>> >> >
>> >> > If we only want to deploy one version of the main report, how would
>> >> > this
>> >> > work if we wanted to have multiple links to the reports, i.e. one in
>> >> > 'Runtime' folder and one in 'Runtime2' folder, with different access
>> >> > permissions on each folder?
>> >> >
>> >> > Cheers
>> >> >
>> >> > "Bruce L-C [MVP]" wrote:
>> >> >
>> >> >> What you want to be doing is doing a jump to the linked report, not
>> >> >> the
>> >> >> base
>> >> >> report. Instead of the name of the report (which assumes it is in
>> >> >> the
>> >> >> current folder, i.e. Deployment folder in your case, do this
>> >> >> instead:
>> >> >>
>> >> >> /Runtime/TheReportYouWant
>> >> >>
>> >> >> This will allow you to jump to the link report as you want. Note
>> >> >> that
>> >> >> it
>> >> >> means you have to deploy to test the link, you won't be able to
>> >> >> test
>> >> >> from
>> >> >> within Report Designer.
>> >> >>
>> >> >>
>> >> >> --
>> >> >> Bruce Loehle-Conger
>> >> >> MVP SQL Server Reporting Services
>> >> >>
>> >> >> "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
>> >> >> news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
>> >> >> >I have a problem using the jump-to feature in a linked report.
>> >> >> > We are deploying all reports to a single folder 'Deployment' (not
>> >> >> > visible
>> >> >> > to
>> >> >> > the browser role) and then creating links to these reports in
>> >> >> > folders
>> >> >> > that
>> >> >> > are visible to the browser role. So from a maintenance point of
>> >> >> > view,
>> >> >> > there
>> >> >> > is only ever one version of the report to update.
>> >> >> > So we have report A that jumps-to report B and both of these are
>> >> >> > deployed
>> >> >> > to
>> >> >> > the 'Deployment' folder which is only visible to developers. We
>> >> >> > then
>> >> >> > create
>> >> >> > links, AL and BL, to both A and B, in another folder called
>> >> >> > 'Runtime'
>> >> >> > folder
>> >> >> > which is visible to end users. End users are able to execute
>> >> >> > report
>> >> >> > AL
>> >> >> > fine
>> >> >> > but when they try to jump-to BL, report manager looks for BL in
>> >> >> > the
>> >> >> > 'Deployment' folder instead of the 'Runtime' folder, therefore,
>> >> >> > errors
>> >> >> > are
>> >> >> > thrown because users don't have access to the 'Deployment
>> >> >> > Folder'.
>> >> >> > How do we force the jump to action on linked reports to remain in
>> >> >> > the
>> >> >> > current folder?
>> >> >> > Obviously this seems to work fine if we are not using linked
>> >> >> > reports.
>> >> >> > Hope this makes sense and any advice would be appreciated.
>> >> >> > TIA
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>|||I have an identical Management requirement (meaning the higher levels of
management have decided to do this, and told me to figure out how).
Like trmpalmer, I published all me report to a "Production Reports" folder,
hidden from browsers. Like trmpalmer, I have been instructed to create
various folders based on management dictated groups, which will also be
duplicated in ADS to give specific groups access to specific reports
designated for that group/department.
Also like trmpalmer, some of my reports use Jump-To to reach other reports.
I tried relative pathing, i.e. " ./Report_2_Name " but that didn't help.
Linked Reports is ideal for me becasue of the administration issue of
maintaining multiple copies of the same report, versus maintaining a single
report and linking to that master copy. I am really hopng to find a solution
that will allow me to use Linked Reports and Jump-To-Report at the same time.
"trmpalmer" wrote:
> Thanks Bruce.
> But to further complicate matters...
> If we only want to deploy one version of the main report, how would this
> work if we wanted to have multiple links to the reports, i.e. one in
> 'Runtime' folder and one in 'Runtime2' folder, with different access
> permissions on each folder?
> Cheers
> "Bruce L-C [MVP]" wrote:
> > What you want to be doing is doing a jump to the linked report, not the base
> > report. Instead of the name of the report (which assumes it is in the
> > current folder, i.e. Deployment folder in your case, do this instead:
> >
> > /Runtime/TheReportYouWant
> >
> > This will allow you to jump to the link report as you want. Note that it
> > means you have to deploy to test the link, you won't be able to test from
> > within Report Designer.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> > news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> > >I have a problem using the jump-to feature in a linked report.
> > > We are deploying all reports to a single folder 'Deployment' (not visible
> > > to
> > > the browser role) and then creating links to these reports in folders that
> > > are visible to the browser role. So from a maintenance point of view,
> > > there
> > > is only ever one version of the report to update.
> > > So we have report A that jumps-to report B and both of these are deployed
> > > to
> > > the 'Deployment' folder which is only visible to developers. We then
> > > create
> > > links, AL and BL, to both A and B, in another folder called 'Runtime'
> > > folder
> > > which is visible to end users. End users are able to execute report AL
> > > fine
> > > but when they try to jump-to BL, report manager looks for BL in the
> > > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors are
> > > thrown because users don't have access to the 'Deployment Folder'.
> > > How do we force the jump to action on linked reports to remain in the
> > > current folder?
> > > Obviously this seems to work fine if we are not using linked reports.
> > > Hope this makes sense and any advice would be appreciated.
> > > TIA
> > >
> >
> >
> >|||I just found a solution, and I wanted to share it here, and I will make a
seperate post.
To accomplish the goal of having a Linked Report perform a Jump-To with a
target report within the same directory as the initial linked report (the
target can also be a linked report), you need some means of "relative
pathing". This can be achieved with the following placed in the Jump to
Report field (click on the fx button or type directly):
=Globals!ReportFolder + "/" + "ReportName"
This will grab the folder the report being run is in. So if you have a
report in runtime2, it would show "/runtime2/ReportName", but would show
"/runtime/ReportName" when run from the runtime folder.
"trmpalmer" wrote:
> Thanks Bruce.
> But to further complicate matters...
> If we only want to deploy one version of the main report, how would this
> work if we wanted to have multiple links to the reports, i.e. one in
> 'Runtime' folder and one in 'Runtime2' folder, with different access
> permissions on each folder?
> Cheers
> "Bruce L-C [MVP]" wrote:
> > What you want to be doing is doing a jump to the linked report, not the base
> > report. Instead of the name of the report (which assumes it is in the
> > current folder, i.e. Deployment folder in your case, do this instead:
> >
> > /Runtime/TheReportYouWant
> >
> > This will allow you to jump to the link report as you want. Note that it
> > means you have to deploy to test the link, you won't be able to test from
> > within Report Designer.
> >
> >
> > --
> > Bruce Loehle-Conger
> > MVP SQL Server Reporting Services
> >
> > "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> > news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> > >I have a problem using the jump-to feature in a linked report.
> > > We are deploying all reports to a single folder 'Deployment' (not visible
> > > to
> > > the browser role) and then creating links to these reports in folders that
> > > are visible to the browser role. So from a maintenance point of view,
> > > there
> > > is only ever one version of the report to update.
> > > So we have report A that jumps-to report B and both of these are deployed
> > > to
> > > the 'Deployment' folder which is only visible to developers. We then
> > > create
> > > links, AL and BL, to both A and B, in another folder called 'Runtime'
> > > folder
> > > which is visible to end users. End users are able to execute report AL
> > > fine
> > > but when they try to jump-to BL, report manager looks for BL in the
> > > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors are
> > > thrown because users don't have access to the 'Deployment Folder'.
> > > How do we force the jump to action on linked reports to remain in the
> > > current folder?
> > > Obviously this seems to work fine if we are not using linked reports.
> > > Hope this makes sense and any advice would be appreciated.
> > > TIA
> > >
> >
> >
> >|||Thanks a million!!
Just what I was looking for :-)
"Rob 'Spike' Stevens" wrote:
> I just found a solution, and I wanted to share it here, and I will make a
> seperate post.
> To accomplish the goal of having a Linked Report perform a Jump-To with a
> target report within the same directory as the initial linked report (the
> target can also be a linked report), you need some means of "relative
> pathing". This can be achieved with the following placed in the Jump to
> Report field (click on the fx button or type directly):
> =Globals!ReportFolder + "/" + "ReportName"
> This will grab the folder the report being run is in. So if you have a
> report in runtime2, it would show "/runtime2/ReportName", but would show
> "/runtime/ReportName" when run from the runtime folder.
> "trmpalmer" wrote:
> > Thanks Bruce.
> >
> > But to further complicate matters...
> >
> > If we only want to deploy one version of the main report, how would this
> > work if we wanted to have multiple links to the reports, i.e. one in
> > 'Runtime' folder and one in 'Runtime2' folder, with different access
> > permissions on each folder?
> >
> > Cheers
> >
> > "Bruce L-C [MVP]" wrote:
> >
> > > What you want to be doing is doing a jump to the linked report, not the base
> > > report. Instead of the name of the report (which assumes it is in the
> > > current folder, i.e. Deployment folder in your case, do this instead:
> > >
> > > /Runtime/TheReportYouWant
> > >
> > > This will allow you to jump to the link report as you want. Note that it
> > > means you have to deploy to test the link, you won't be able to test from
> > > within Report Designer.
> > >
> > >
> > > --
> > > Bruce Loehle-Conger
> > > MVP SQL Server Reporting Services
> > >
> > > "trmpalmer" <trmpalmer@.discussions.microsoft.com> wrote in message
> > > news:041781FC-7486-4AC6-A689-EF00533DED12@.microsoft.com...
> > > >I have a problem using the jump-to feature in a linked report.
> > > > We are deploying all reports to a single folder 'Deployment' (not visible
> > > > to
> > > > the browser role) and then creating links to these reports in folders that
> > > > are visible to the browser role. So from a maintenance point of view,
> > > > there
> > > > is only ever one version of the report to update.
> > > > So we have report A that jumps-to report B and both of these are deployed
> > > > to
> > > > the 'Deployment' folder which is only visible to developers. We then
> > > > create
> > > > links, AL and BL, to both A and B, in another folder called 'Runtime'
> > > > folder
> > > > which is visible to end users. End users are able to execute report AL
> > > > fine
> > > > but when they try to jump-to BL, report manager looks for BL in the
> > > > 'Deployment' folder instead of the 'Runtime' folder, therefore, errors are
> > > > thrown because users don't have access to the 'Deployment Folder'.
> > > > How do we force the jump to action on linked reports to remain in the
> > > > current folder?
> > > > Obviously this seems to work fine if we are not using linked reports.
> > > > Hope this makes sense and any advice would be appreciated.
> > > > TIA
> > > >
> > >
> > >
> > >
Friday, March 23, 2012
Joins in Crystal Reports
Hi,
I'm newbie in Crystal report. I've a query which i'm unable to implement in CR. Eventhough the query looks simple because of the join condition I'm struggling . Pls help me to implement the join condition. I run the query in DB2
select sum(bank_ledger_bal_amt),calendar_date
from table_a a
inner join table_date b
on a.bank_acct_eff_dt <= b.calendar_date
and a.bank_acct_disc_dt > b.calendar_date
where month_id = 'feb'
group by b.calendar_date
order by b.calendar_date
;
Thanks,
JashUse the add command of Crystal and paste in your SQL query in there.
GJ|||Sorry I didnt get what do you mean|||In the Database Expert there is an option to select "Add Command" there you can type out your sql. Crystal will let you know if there is an error in your SQL.
GJsql
I'm newbie in Crystal report. I've a query which i'm unable to implement in CR. Eventhough the query looks simple because of the join condition I'm struggling . Pls help me to implement the join condition. I run the query in DB2
select sum(bank_ledger_bal_amt),calendar_date
from table_a a
inner join table_date b
on a.bank_acct_eff_dt <= b.calendar_date
and a.bank_acct_disc_dt > b.calendar_date
where month_id = 'feb'
group by b.calendar_date
order by b.calendar_date
;
Thanks,
JashUse the add command of Crystal and paste in your SQL query in there.
GJ|||Sorry I didnt get what do you mean|||In the Database Expert there is an option to select "Add Command" there you can type out your sql. Crystal will let you know if there is an error in your SQL.
GJsql
Subscribe to:
Posts (Atom)