| Author |
 Topic  |
|
|
thm
29 Posts |
 Posted - 03/16/2005 : 11:36:13
|
When you design MSRS report, you can do jump-to action within the report, but when I pull it into RP2.0, when you open up the MSRS report and click on the jump-to report, it bring up a new report with out the RP2.0 UI. is there a solution not to loose the RP2.0 UI.
thanks |
|
|
code_slayer_bkk
Thailand
6 Posts |
Posted - 03/30/2005 : 07:08:47
|
quote:
Originally posted by thm
When you design MSRS report, you can do jump-to action within the report, but when I pull it into RP2.0, when you open up the MSRS report and click on the jump-to report, it bring up a new report with out the RP2.0 UI. is there a solution not to loose the RP2.0 UI.
thanks
Sorry on the first reply - was not paying attention!
MSRS will always launch a Navigation (Jump To) in the current page browser default - which you have seen from the first launch of the MSRS report which opened IE.x and then from there you "jumped to" another MSRS report which used the browser mode the first MSRS report was that was displayed.
But this is normal for MSRS - MSRS calls a report that is MSRS same same!
This happens to me all the time when using MSRS from SharePoint or DotNetNuke.
But this should not be a problem for your users they just <back> from the "jumped to" report to the calling report - and then they exit from the caller and they are back in the frame work! This behavior is normal for called (JUMPED TO) reports...
Hope this helps you -
Best Regards - Joe
¹Ó¿¾¾ÃËÔ¿×à¹Ò |
 |
|
|
code_slayer_bkk
Thailand
6 Posts |
Posted - 03/30/2005 : 07:26:58
|
quote:
Originally posted by thm
When you design MSRS report, you can do jump-to action within the report, but when I pull it into RP2.0, when you open up the MSRS report and click on the jump-to report, it bring up a new report with out the RP2.0 UI. is there a solution not to loose the RP2.0 UI.
thanks
Let me re-phrase this:
1. You call a MSRS report from the portal which is really a URL link (which this url link points to an MSRS report)
the "call" from the portal did not have any environment variables, etc., etc.,etc. passed to the MSRS REPORT to indicate anything indicating portal or environment variables (just like opening a web page on a site then doing a <FILE> then <OPEN> and then entering a new www site - nothing from the first site is going to be passed to the second site. The only way you get back is the <BACK> button which your browser conveniently saves for you.
2. The CALLED MSRS report executes - displays data and a chart and you have a navigational link (jump to) in the chart or from a hyperlink in the data. The User clicks on the navigation link!
3. The new MSRS report is displayed This program has no clue (not really true) who called it - the only way you get back to the "caller" is hit the back button -------- This report has no idea what the initial portal was associated with the caller or who launched it...
It is OKAY - the User only need to know to hit the <BACK> button on the browser and they will be returned to the caller the caller can end and you are back in the portal so to say!
Hope I have been of some help!
Best Regards,
Joe
¹Ó¿¾¾ÃËÔ¿×à¹Ò |
|
|
|
thm
29 Posts |
Posted - 04/12/2005 : 14:50:53
|
Joe:
Thanks for the reply, but I was hoping for someone to say that I can just edit the Jump-to link with the RP link\view.asp? Embedded in front of the MSRS jump-to report name and parms before I pull it into RP, but I guess this is not the case. Anyway, I understand what you are trying to say, but it’s an ugly solution.
I hope it will be better next version.
thanks
quote:
Originally posted by code_slayer_bkk
quote:
Originally posted by thm
When you design MSRS report, you can do jump-to action within the report, but when I pull it into RP2.0, when you open up the MSRS report and click on the jump-to report, it bring up a new report with out the RP2.0 UI. is there a solution not to loose the RP2.0 UI.
thanks
Let me re-phrase this:
1. You call a MSRS report from the portal which is really a URL link (which this url link points to an MSRS report)
the "call" from the portal did not have any environment variables, etc., etc.,etc. passed to the MSRS REPORT to indicate anything indicating portal or environment variables (just like opening a web page on a site then doing a <FILE> then <OPEN> and then entering a new www site - nothing from the first site is going to be passed to the second site. The only way you get back is the <BACK> button which your browser conveniently saves for you.
2. The CALLED MSRS report executes - displays data and a chart and you have a navigational link (jump to) in the chart or from a hyperlink in the data. The User clicks on the navigation link!
3. The new MSRS report is displayed This program has no clue (not really true) who called it - the only way you get back to the "caller" is hit the back button -------- This report has no idea what the initial portal was associated with the caller or who launched it...
It is OKAY - the User only need to know to hit the <BACK> button on the browser and they will be returned to the caller the caller can end and you are back in the portal so to say!
Hope I have been of some help!
Best Regards,
Joe
¹Ó¿¾¾ÃËÔ¿×à¹Ò
|
|
|
| |
Topic |
|
|
|
Report Portal
How do you handle Jump to in MSRS report
