Thanks, unfortunately, Open document doesn’t help much. Most of the linkage answers I found were primarily dealing with a Windows environment.
Going through FullClient and UNIX, there doesn’t seem to be any clear cut way of doing such a link. At least, I can’t find it yet.
For linking the reports, we are using the server name as part of the href value , in real scenario if we migrate the reports from development to production environment , it might have a different server name. In that case do we need to manually go to each report to change href value to point to the production server name or is there any alternative to do that.
I mean a variable that holds the Server Name and Port Number which I need to use in all of my master reports to link to the details. The bottomline is If I deploy my reports to the production I need not change my server name and port number in all of my master report href link, instead I could just change in one place that would change all the href values. FYI, I am not using VB application.
It sounds like you’re referring to a universe object. Your href code can be in the select of an object, and you can change it at anytime, allowing your reports to grab the update.
What about the doc id? Don’t you have to put in the doc id for every report you want to link to? Isn’t the doc id different for each environment? You may still have to manually code this in.
Well, I tried to create an configuration table that holds the server name, port number and created the object in the universe by refereing that column. I get an error(Incompatible variable types) when I try to use the value as a part of the href in the master detail report for the key value since the master report has no join with the configuration table.
In v6 you don’t need the DocID number in the link. The Doc Name and Domain are all that is needed. This is a good thing, since the Doc ID number isn’t as easy to find as it was in v5.
I just tried my link using a href instead of location=, and it worked the same way. Here’s my complete string:
<a href="/wijsp/scripts/openDocument.jsp?sType=wid&sRepoType=Corporate&sDoc=Performance+Production&iDocID=21098&lsM1{lots of prompts here}&sRefresh=N">click</a>
I did use Format as HTML instead of Hyperlink, don’t know if that would make a difference…
Weird - I tried it with a rep and that worked too. Can’t think of anything else – can you do a view source from Infoview to see exactly how the link is being built?
Correct me if I am wrong. I guess the reason why I am not able to try with relative path is, since my documents are physically stored in the repository and not in the app server location, by looking at your href example it might be possible if I would have created those reports through webi and it might have stored as .wid in the server and in that case using the relative path would access the report. In my case I have created my reports through the client version and I publish it to the corporate document and which requires the server name to part of the Href value. And I don’t know why BO doesn’t have much of flexibility in configuring the server name and other system level configuration.