I have a proc report with embedded links to another report. I use the script below to generate the linked column. It does not seem to be working when I create the stored a stored proc report in Web Report Studio.
I thought WRS 4.2 finally supported embedded links.
proc report data=Survey_Report(where=(question not in (11,8,12,13,14,15) and ReasonForCall='Screener'));
column SurveyDate AverageScore, Question;
define Question/across order=data;
define AverageScore/analysis mean '' style(column=background=score.};
Instead of proc report, you could use data _null_ statements to custom define the URL as <a href="http://www.google.com" target=new>test</a>
This would force the url to open in a new window - outside of the Web Report Studio app.
Otherwise, the default URL/HREF that PROC REPORT builds is:
I believe the default TARGET behavior is the browser setting, which is, I think to reuse the same window -- and probably WRS is not happy about that -- the Portal doesn't care -- it allows you to use browser windows as you want.
As far as I know, the only way to get TARGET= into the URL created with ODS is to change the STYLE template attribute HREFTARGET. However, the downside of this is that WRS -generally- does not use any style template that you specify. So, for example, if you specified this in a stored process:
...rest of code;
Many of the Enterprise Intelligence Platform client applications (like the Portal or EG) would use the SASWEB style template to apply style when the output was rendered. However, WRS does -not- use the SAS style template specified in _ODSSTYLE -- it uses the styles as defined in the XML behind the scenes with WRS -- since the any output type that you specify is SASReport XML by the time the report gets to WRS. Even if you explicitly do this:
...rest of code;
and indicate that you want HTML results, only client apps that can -receive- HTML results will use the _ODSDEST parameter. For example, EG, the Portal, the SAS Add-in for Microsoft Office (Word and Excel) will all receive HTML results. However, PowerPoint and Web Report Studio will ONLY receive SASReport XML results --- which are NOT the same as HTML. So these 2 client apps change or ignore your _ODSDEST override and use SASReport XML to create the report. The reason you need to test your stored process in all the client apps that will be invoking the stored process is for just this reason -- a stored process might not look or work the same way in PowerPoint or WRS as it works in EG or the Portal.
So, in building your URL, you have several issues at work:
1) TARGET=NEW might work in WRS
2) WRS is receiving and rendering SASReport XML -- not HTML
3) if you change your style template to alter the HREFTARGET attribute, WRS does not use style templates -- so you'd have to change the CSS information in the XML that runs rendering in WRS.
4) there was a Tech Support note about HREFTARGET not working in CSS: http://support.sas.com/kb/9/313.html (supposedly this was fixed in SAS 9.1, so you'd have to check with Tech Support whether HREFTARGET in CSS will work now and with the WRS CSS).
5) SASReport XML is not the same as HTML -- so you might need to code hyperlinks differently for SASReport XML (such as used in WRS) than for HTML results (such as used in other client apps).
Angela has pointed you to some examples sites in her post and if you can't get what you need by looking at the examples, then, you might wish to open a track with Tech Support.
I was anticipating a similar answer, but just gave it a try. I have a report layout that is not feasible with the crosstab in the WRS, the only way I can get around is using Proc Report, but the challenge is with the Linked Reports.