I'm using Visual Studio 2008, and SQL 2008 Developer edition. I have Microsoft SQL Server Reporting Services Designers Version 10.0.1600.22 I'm rendering reports with Microsoft.ReportViewer.WebForms, Version 9.0.0.0.
I've had reports working with the 'Go to Report' action (Hyperlink action in the rdl) for some time now. I need now to have some reports link out of SSRS to a custom application. I had planned on setting a 'Jump to URL' action on certain textboxes. When I do this in the VS designer, and preview the report, a new tab opens in my broser. All well and good.
However, if I render a deployed report (in html) either in my app using ReportViewer or directly out of the Report Manager, I get the hotspot with the 'Finger' appearing over the textbox, but clicking on the link does nothing.
At first I thought this was a data error because I knew that this was the behavior you observed if the url wasn't valid, but I've verified my data and tested the report with trivial url's like http://www.microsoft.com. It does in fact work in VS designer (valid url) but it does not work in ReportViewer.
1) Does anyone have a deployed 2008 report which renders the jump to url correctly in html? I've seen alot of questions about 'Go to Report', but that's not my problem.
2) Can anyone think of something I'm not thinking of, like is there some sort of security setting on SSRS that stops reporting services from linking out?
3) Is this a Microsoft bug?
I would really like a response on this. IF this is a MS error, then this is the third major show stopping bug I've come across in SSRS 2008. The previous two - incorrectly rendering charts with dynamic sizing and not correctly passing data to an adjacent row group when there was also a column group in the tablix - cost me a couple days of work, but I could work around them. I don't see a work around in this case because the url is not static, and isn't something I can just add to the rendered report with a javascript or css hack.
I would like to know ASAP whether or not this is a bug because if it is I need to go to marketting and tell them to remove references to this functionality from upcoming marketing releases.
Thanks,
Matt
I've had reports working with the 'Go to Report' action (Hyperlink action in the rdl) for some time now. I need now to have some reports link out of SSRS to a custom application. I had planned on setting a 'Jump to URL' action on certain textboxes. When I do this in the VS designer, and preview the report, a new tab opens in my broser. All well and good.
However, if I render a deployed report (in html) either in my app using ReportViewer or directly out of the Report Manager, I get the hotspot with the 'Finger' appearing over the textbox, but clicking on the link does nothing.
At first I thought this was a data error because I knew that this was the behavior you observed if the url wasn't valid, but I've verified my data and tested the report with trivial url's like http://www.microsoft.com. It does in fact work in VS designer (valid url) but it does not work in ReportViewer.
1) Does anyone have a deployed 2008 report which renders the jump to url correctly in html? I've seen alot of questions about 'Go to Report', but that's not my problem.
2) Can anyone think of something I'm not thinking of, like is there some sort of security setting on SSRS that stops reporting services from linking out?
3) Is this a Microsoft bug?
I would really like a response on this. IF this is a MS error, then this is the third major show stopping bug I've come across in SSRS 2008. The previous two - incorrectly rendering charts with dynamic sizing and not correctly passing data to an adjacent row group when there was also a column group in the tablix - cost me a couple days of work, but I could work around them. I don't see a work around in this case because the url is not static, and isn't something I can just add to the rendered report with a javascript or css hack.
I would like to know ASAP whether or not this is a bug because if it is I need to go to marketting and tell them to remove references to this functionality from upcoming marketing releases.
Thanks,
Matt