jumping to a report

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

jump to url option with _blank

I am trying to set up a link using the navigation/hyperlink action/jump to
url feature of reporting services(Right Click ->Advanced->Navigation->Jump To
Url).
When I click on the hyperlink, I would like the navigation target to be a
new form (_blank), NOT the existing one. I have tried the following code
with some success
="javascript:void(window.open('" & Fields!feature_url.Value & "','_blank'))"
As you can see the actual url is contained in: " & Fields!feature_url.Value
& "
If I preview my report in Visual Studio, click on the hyperlink it will
launch a page that contains the entire line:
="javascript:void(window.open('" & Fields!feature_url.Value & "','_blank'))"
in the browser's url field, it then launches a second page with the correct
url.
Unfortunately, it doesn't work at all from the report server...I just get a
page with the entire line and then nothing.
Does anyone know how to do this? Here's the html if that's of any use.
<Action>
<Hyperlink>="javascript:void(window.open('" & Fields!feature_url.Value
& "','_blank'))"
</Hyperlink>
</Action>I create a test report and it works fine...I have SP2.
Check the post "Please Help"
Jeronimo Vogt
"beeyule" <beeyule@.discussions.microsoft.com> wrote in message
news:ED8D1700-FA0E-4E58-B8C4-CEC4AC367B6C@.microsoft.com...
> I am trying to set up a link using the navigation/hyperlink action/jump to
> url feature of reporting services(Right Click ->Advanced->Navigation->Jump
To
> Url).
> When I click on the hyperlink, I would like the navigation target to be a
> new form (_blank), NOT the existing one. I have tried the following code
> with some success
> ="javascript:void(window.open('" & Fields!feature_url.Value &
"','_blank'))"
> As you can see the actual url is contained in: " &
Fields!feature_url.Value
> & "
> If I preview my report in Visual Studio, click on the hyperlink it will
> launch a page that contains the entire line:
> ="javascript:void(window.open('" & Fields!feature_url.Value &
"','_blank'))"
> in the browser's url field, it then launches a second page with the
correct
> url.
> Unfortunately, it doesn't work at all from the report server...I just get
a
> page with the entire line and then nothing.
> Does anyone know how to do this? Here's the html if that's of any use.
> <Action>
> <Hyperlink>="javascript:void(window.open('" & Fields!feature_url.Value
> & "','_blank'))"
> </Hyperlink>
> </Action>
>
>
>|||bee,
Please check the url of the first report
dont type in localhost/reorts - type <yourservername>/reports.
Hope this helps
"beeyule" wrote:
> I am trying to set up a link using the navigation/hyperlink action/jump to
> url feature of reporting services(Right Click ->Advanced->Navigation->Jump To
> Url).
> When I click on the hyperlink, I would like the navigation target to be a
> new form (_blank), NOT the existing one. I have tried the following code
> with some success
> ="javascript:void(window.open('" & Fields!feature_url.Value & "','_blank'))"
> As you can see the actual url is contained in: " & Fields!feature_url.Value
> & "
> If I preview my report in Visual Studio, click on the hyperlink it will
> launch a page that contains the entire line:
> ="javascript:void(window.open('" & Fields!feature_url.Value & "','_blank'))"
> in the browser's url field, it then launches a second page with the correct
> url.
> Unfortunately, it doesn't work at all from the report server...I just get a
> page with the entire line and then nothing.
> Does anyone know how to do this? Here's the html if that's of any use.
> <Action>
> <Hyperlink>="javascript:void(window.open('" & Fields!feature_url.Value
> & "','_blank'))"
> </Hyperlink>
> </Action>
>
>
>|||"RP" wrote:
> bee,
> Please check the url of the first report
> dont type in localhost/reorts - type <yourservername>/reports.
> Hope this helps
> "beeyule" wrote:
> > I am trying to set up a link using the navigation/hyperlink action/jump to
> > url feature of reporting services(Right Click ->Advanced->Navigation->Jump To
> > Url).
> >
> > When I click on the hyperlink, I would like the navigation target to be a
> > new form (_blank), NOT the existing one. I have tried the following code
> > with some success
> >
> > ="javascript:void(window.open('" & Fields!feature_url.Value & "','_blank'))"
> >
> > As you can see the actual url is contained in: " & Fields!feature_url.Value
> > & "
> >
> > If I preview my report in Visual Studio, click on the hyperlink it will
> > launch a page that contains the entire line:
> >
> > ="javascript:void(window.open('" & Fields!feature_url.Value & "','_blank'))"
> >
> > in the browser's url field, it then launches a second page with the correct
> > url.
> >
> > Unfortunately, it doesn't work at all from the report server...I just get a
> > page with the entire line and then nothing.
> >
> > Does anyone know how to do this? Here's the html if that's of any use.
> >
> > <Action>
> > <Hyperlink>="javascript:void(window.open('" & Fields!feature_url.Value
> > & "','_blank'))"
> > </Hyperlink>
> > </Action>
> >
> >
> >
> >
> >
> >
bee,
> Please check the url of the first report
> dont type in localhost/reorts - type <yourservername>/reports.
I have sp4...
I'm not typing in the localhost address. The url to the report server is
determined by the "Fields!feature_url.Value" field.
The report itself opens without incident. When I click on the hyperlink
located within the report column I get a directed to a web page with the url:
javascript:void(window.open('http://websiteaddress/app/Page.aspx?ID=1','_blank'))
the url contained within the code is correct, it just doesn't behave the way
I had anticipated.|||We are on SP1 and found the "LinkTarget" property does NOT work the way it is
supposed to on the report server (be careful when testing in the Visual
Studio designer - it opens a new page because you are running in VS.)
The Javascript code to open a new window does NOT work in SP1. SP2 is
supposed to have fixed this - I have not yet found out if that is actually
the case.
Tom
"beeyule" wrote:
>
> "RP" wrote:
> > bee,
> > Please check the url of the first report
> > dont type in localhost/reorts - type <yourservername>/reports.
> >
> > Hope this helps
> >
> > "beeyule" wrote:
> >
> > > I am trying to set up a link using the navigation/hyperlink action/jump to
> > > url feature of reporting services(Right Click ->Advanced->Navigation->Jump To
> > > Url).
> > >
> > > When I click on the hyperlink, I would like the navigation target to be a
> > > new form (_blank), NOT the existing one. I have tried the following code
> > > with some success
> > >
> > > ="javascript:void(window.open('" & Fields!feature_url.Value & "','_blank'))"
> > >
> > > As you can see the actual url is contained in: " & Fields!feature_url.Value
> > > & "
> > >
> > > If I preview my report in Visual Studio, click on the hyperlink it will
> > > launch a page that contains the entire line:
> > >
> > > ="javascript:void(window.open('" & Fields!feature_url.Value & "','_blank'))"
> > >
> > > in the browser's url field, it then launches a second page with the correct
> > > url.
> > >
> > > Unfortunately, it doesn't work at all from the report server...I just get a
> > > page with the entire line and then nothing.
> > >
> > > Does anyone know how to do this? Here's the html if that's of any use.
> > >
> > > <Action>
> > > <Hyperlink>="javascript:void(window.open('" & Fields!feature_url.Value
> > > & "','_blank'))"
> > > </Hyperlink>
> > > </Action>
> > >
> > >
> > >
> > >
> > >
> > >
> bee,
> > Please check the url of the first report
> > dont type in localhost/reorts - type <yourservername>/reports.
>
> I have sp4...
> I'm not typing in the localhost address. The url to the report server is
> determined by the "Fields!feature_url.Value" field.
> The report itself opens without incident. When I click on the hyperlink
> located within the report column I get a directed to a web page with the url:
> javascript:void(window.open('http://websiteaddress/app/Page.aspx?ID=1','_blank'))
> the url contained within the code is correct, it just doesn't behave the way
> I had anticipated.
>
>|||Hmm, not sure why it isn't working correctly for you. I suspect something in
how you are creating the URL. Are you using jump to URL? I have had this
working in both SP1 and SP2 and I know others have as well. Here is a URL
that works for me (opening a new window). One thing to note, it does not
work from VS, you have to deploy it. Try copying and pasting the below into
the jump to URL and give it a try.
= "javascript:void(window.open('http://www.google.com','_blank'))"
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"ASP Yaboh" <ASPYaboh@.discussions.microsoft.com> wrote in message
news:8F5897A0-09D1-4565-8573-5ADCE6191360@.microsoft.com...
> We are on SP1 and found the "LinkTarget" property does NOT work the way it
> is
> supposed to on the report server (be careful when testing in the Visual
> Studio designer - it opens a new page because you are running in VS.)
> The Javascript code to open a new window does NOT work in SP1. SP2 is
> supposed to have fixed this - I have not yet found out if that is actually
> the case.
> Tom
> "beeyule" wrote:
>>
>> "RP" wrote:
>> > bee,
>> > Please check the url of the first report
>> > dont type in localhost/reorts - type <yourservername>/reports.
>> >
>> > Hope this helps
>> >
>> > "beeyule" wrote:
>> >
>> > > I am trying to set up a link using the navigation/hyperlink
>> > > action/jump to
>> > > url feature of reporting services(Right
>> > > Click ->Advanced->Navigation->Jump To
>> > > Url).
>> > >
>> > > When I click on the hyperlink, I would like the navigation target to
>> > > be a
>> > > new form (_blank), NOT the existing one. I have tried the following
>> > > code
>> > > with some success
>> > >
>> > > ="javascript:void(window.open('" & Fields!feature_url.Value &
>> > > "','_blank'))"
>> > >
>> > > As you can see the actual url is contained in: " &
>> > > Fields!feature_url.Value
>> > > & "
>> > >
>> > > If I preview my report in Visual Studio, click on the hyperlink it
>> > > will
>> > > launch a page that contains the entire line:
>> > >
>> > > ="javascript:void(window.open('" & Fields!feature_url.Value &
>> > > "','_blank'))"
>> > >
>> > > in the browser's url field, it then launches a second page with the
>> > > correct
>> > > url.
>> > >
>> > > Unfortunately, it doesn't work at all from the report server...I just
>> > > get a
>> > > page with the entire line and then nothing.
>> > >
>> > > Does anyone know how to do this? Here's the html if that's of any
>> > > use.
>> > >
>> > > <Action>
>> > > <Hyperlink>="javascript:void(window.open('" &
>> > > Fields!feature_url.Value
>> > > & "','_blank'))"
>> > > </Hyperlink>
>> > > </Action>
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >
>> bee,
>> > Please check the url of the first report
>> > dont type in localhost/reorts - type <yourservername>/reports.
>>
>> I have sp4...
>> I'm not typing in the localhost address. The url to the report server is
>> determined by the "Fields!feature_url.Value" field.
>> The report itself opens without incident. When I click on the hyperlink
>> located within the report column I get a directed to a web page with the
>> url:
>> javascript:void(window.open('http://websiteaddress/app/Page.aspx?ID=1','_blank'))
>> the url contained within the code is correct, it just doesn't behave the
>> way
>> I had anticipated.
>>
>>|||I'm pretty certain we thoroughly flogged this issue, but I will deploy a test
report later today with that exact link just to be certain.
Thank you.
"Bruce L-C [MVP]" wrote:
> Hmm, not sure why it isn't working correctly for you. I suspect something in
> how you are creating the URL. Are you using jump to URL? I have had this
> working in both SP1 and SP2 and I know others have as well. Here is a URL
> that works for me (opening a new window). One thing to note, it does not
> work from VS, you have to deploy it. Try copying and pasting the below into
> the jump to URL and give it a try.
> = "javascript:void(window.open('http://www.google.com','_blank'))"
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "ASP Yaboh" <ASPYaboh@.discussions.microsoft.com> wrote in message
> news:8F5897A0-09D1-4565-8573-5ADCE6191360@.microsoft.com...
> > We are on SP1 and found the "LinkTarget" property does NOT work the way it
> > is
> > supposed to on the report server (be careful when testing in the Visual
> > Studio designer - it opens a new page because you are running in VS.)
> >
> > The Javascript code to open a new window does NOT work in SP1. SP2 is
> > supposed to have fixed this - I have not yet found out if that is actually
> > the case.
> >
> > Tom
> >
> > "beeyule" wrote:
> >
> >>
> >>
> >> "RP" wrote:
> >>
> >> > bee,
> >> > Please check the url of the first report
> >> > dont type in localhost/reorts - type <yourservername>/reports.
> >> >
> >> > Hope this helps
> >> >
> >> > "beeyule" wrote:
> >> >
> >> > > I am trying to set up a link using the navigation/hyperlink
> >> > > action/jump to
> >> > > url feature of reporting services(Right
> >> > > Click ->Advanced->Navigation->Jump To
> >> > > Url).
> >> > >
> >> > > When I click on the hyperlink, I would like the navigation target to
> >> > > be a
> >> > > new form (_blank), NOT the existing one. I have tried the following
> >> > > code
> >> > > with some success
> >> > >
> >> > > ="javascript:void(window.open('" & Fields!feature_url.Value &
> >> > > "','_blank'))"
> >> > >
> >> > > As you can see the actual url is contained in: " &
> >> > > Fields!feature_url.Value
> >> > > & "
> >> > >
> >> > > If I preview my report in Visual Studio, click on the hyperlink it
> >> > > will
> >> > > launch a page that contains the entire line:
> >> > >
> >> > > ="javascript:void(window.open('" & Fields!feature_url.Value &
> >> > > "','_blank'))"
> >> > >
> >> > > in the browser's url field, it then launches a second page with the
> >> > > correct
> >> > > url.
> >> > >
> >> > > Unfortunately, it doesn't work at all from the report server...I just
> >> > > get a
> >> > > page with the entire line and then nothing.
> >> > >
> >> > > Does anyone know how to do this? Here's the html if that's of any
> >> > > use.
> >> > >
> >> > > <Action>
> >> > > <Hyperlink>="javascript:void(window.open('" &
> >> > > Fields!feature_url.Value
> >> > > & "','_blank'))"
> >> > > </Hyperlink>
> >> > > </Action>
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >> > >
> >>
> >> bee,
> >> > Please check the url of the first report
> >> > dont type in localhost/reorts - type <yourservername>/reports.
> >>
> >>
> >> I have sp4...
> >>
> >> I'm not typing in the localhost address. The url to the report server is
> >> determined by the "Fields!feature_url.Value" field.
> >>
> >> The report itself opens without incident. When I click on the hyperlink
> >> located within the report column I get a directed to a web page with the
> >> url:
> >>
> >> javascript:void(window.open('http://websiteaddress/app/Page.aspx?ID=1','_blank'))
> >>
> >> the url contained within the code is correct, it just doesn't behave the
> >> way
> >> I had anticipated.
> >>
> >>
> >>
> >>
>
>

jump to URL navigation feature

I am using the navigation/hyperlink action/jump to url feature of reporting services(Right Click ->Advanced->Navigation->Jump To Url).In my environment the url comes from the database so I use thefollowing code in the "jump to url" field: =Fields!feature_url.Value.
I want to open a new window(_blank) when I click on the link but am having difficulties. I found some code
"void(window.open('& =Fields!feature_url &','_blank'))"
but haven't yet gotten it to work. I am entering this code directly into the "jump to url" field.
Does anyone have any ideas?
I left out a bit of important info...
If I use this:
="javascript:void(window.open('http://www.google.com','_blank'))"
I will be properly directed to google, so it looks like this piece ofcode works. I'm having trouble replacing the google urlwith "=Fields!feature_url.Value"

|||Hi, I don't know how you manage to have that piece of javascript working... I copy/pasted the string you posted and it is taked as a URL literally ... so obviosly it doesn't work.
I want that the Report show itself in an IFRAME and not in a new window, but should be just changing the TARGET property in the windows.open, isn't it?
May be this is a problem with my OS... Win2003 Server.
If you could help me... I'll be grateful.
Thanks in advance,
Matías|||

To call up a javascript window link from the "Jump To URL" functionality in Reporting Services SP2 Hotfix 1 applied, use:
="javascript:void(window.open('" & Fields!feature_url &"','_blank'))"
If you want it to direct to an iframe, make your iframe on your page:
<iframe name="MyFrameName"></iframe>
and make your link:
="javascript:void(window.open('" & Fields!feature_url &"','MyFrameName'))"
This works in IE6, but I can't say for the other browsers.

|||

The reportviewer control has an attribute named "HyperlinkTarget"

so Yo can have somthing like:

<rsweb:ReportViewerID="reportViewer"runat="server"Font-Names="Verdana"Font-Size="8pt"

Width="100%"Height="800px"HyperlinkTarget="_blank">

</rsweb:ReportViewer>

Jump to URL for pdf file

Does anyone know if it is possible to use the Jump To URL feature to display
a pdf file?
It seem like it should be possible because I can upload the pdf to a
Reporting Services folder and then use Report Manager to open and display it,
but I can't seem to get it to work in a report. Possibly due to a syntax
problem?...
Thanks,
SteveYes you can do it. I just tried on some word documents that I have deployed.
First, to make sure we are on the same page. You need to bring your PDF file
into your project and deploy it. Next do this:
="javascript:void(window.open('" & Globals!ReportServerUrl &
"?/FolderName/Documentname.pdf','_blank'))"
or if don't want it open in another window do this:
=Globals!ReportServerUrl & "?/SomeFolder/SomeDocument.PDF"
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Steve" <MyNoSpam@.NoSpam.org> wrote in message
news:325FCAA0-0C98-48DE-A50F-28FCC264B48B@.microsoft.com...
> Does anyone know if it is possible to use the Jump To URL feature to
> display
> a pdf file?
> It seem like it should be possible because I can upload the pdf to a
> Reporting Services folder and then use Report Manager to open and display
> it,
> but I can't seem to get it to work in a report. Possibly due to a syntax
> problem?...
> Thanks,
> Steve|||Works great -- very cool. And I will use your open new window trick in a
different application. I was missing the "?".
Regards,
Steve
"Bruce L-C [MVP]" wrote:
> Yes you can do it. I just tried on some word documents that I have deployed.
> First, to make sure we are on the same page. You need to bring your PDF file
> into your project and deploy it. Next do this:
> ="javascript:void(window.open('" & Globals!ReportServerUrl &
> "?/FolderName/Documentname.pdf','_blank'))"
> or if don't want it open in another window do this:
> =Globals!ReportServerUrl & "?/SomeFolder/SomeDocument.PDF"
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Steve" <MyNoSpam@.NoSpam.org> wrote in message
> news:325FCAA0-0C98-48DE-A50F-28FCC264B48B@.microsoft.com...
> > Does anyone know if it is possible to use the Jump To URL feature to
> > display
> > a pdf file?
> >
> > It seem like it should be possible because I can upload the pdf to a
> > Reporting Services folder and then use Report Manager to open and display
> > it,
> > but I can't seem to get it to work in a report. Possibly due to a syntax
> > problem?...
> >
> > Thanks,
> > Steve
>
>

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