Hi Listners,
I have 3 tables namely company,contact and Product tables. I want set up a hierarchy to perform a drill down report. The drill down report should look like…
company details on the top level ( company name, addresses details)…
when clicking on company name drill down to Contact details(contact persons, address, emailadress etc.,)…
when clicking on Contact name drill down to Product details( product number, serial number, etc…,)
How can we accomplish on webi How do I set up a hierarchy in the designer to accomplish this? Any suggestions/ideas please .
Any suggestions how we can do this on webi(drill across)? or Is this can only be done with full client. Where do I search for opendocument… Pl guide me. .
Steve – doesn’t the OpenDocument function used in the example you hyperlinked above only work if one has SDK? I did a demo once based on something you put together (I think), and had slightly different format because we do not have SDK.
I defined a variable in my full-client report, with a cell format that is checked as “Read as HTML” on the Number tab.
Ignoring the spaces and carriage returns, a format that worked for me looked like this sample:
The + sign is used for concatenating strings together in Reporter.
The Char(34) is a way to get an embedded quote mark into the final string.
The “child” report being called (sDoc) is my “StaffCountsSchoolsA” report. It’s best to not have any spaces in the name.
The “type” (sTyp) R is a full-client report (W would be for WebI)
The iDocId is the repository document id – you have to query against the repository tables to find that (I used another query tool). (Obviously, the child document has to first be exported to the repository.) In this case, it is 871.
The document repository (sRepo) is, in my case, cosmo_doc
The sOpen parameter says to open the report. I don’t know if it’s required, but it got in as I was trying to get this to work!
The lsS parameters are single-response parameters to be passed to the child report – its prompts. (I made them short and without spaces), followed by an equal sign, and then concatenate in the variable/object from THIS report whose value to use – which the user clicks. (Or, concatenate in the response to a previously-asked prompt.)
The “target=_self” causes a window with “breadcrumbs” to parent report(s), rather than launching a new window.
The TITLE="…" creates a little description pop-up window when the user’s mouse hovers over the hyperlink.
The just after the closing “>” of the hyperlink is the object/variable, and what gets displayed to the user in the parent report.
There is an OpenDocument function in there also. But the method you described is exactly what I was referring to. You can do it in the report on by building objects in the universe.
I am trying to follow the example that you posted on Dec 13, 2002 about Linking WebIntelligence Reports. The example is interesting because it shows us a way to pass prompt selections from the main to the child report. However, when I try to create an object in Designer, I am getting the following error message:
Parse Failed: ‘UserResponse’ is not a recognized built-in function name.
Do we need to create a function ‘UserResponse’? If yes, how do we create it?
UserResponse is a report function, not a Designer function. Your report should already have prompts in it. Those prompts can either be built in the Query Panel or in the universe using @variable or @prompt.
Than you a lot.
This code permit do not generate a lot of rows during the execute of the sql, i 'hope this permit a better report performance.
For view the reports in infoview, i use “in function of the browser” option
but the only thing that doesn’t work is the little description pop-up windows when the user’s mouse hovers over the hyperlink.(only standard html work fine)
If i use pdf option i’ve got a lot of problems:
1)during the exploration (with opendocument function) some blue frame appear under reports.I think this is a BO bugs,
2)if i move the mouse over the hyperlink i 'll see all the code about the open document function.
What do you think about??
The blue frame is not a bug. That’s how it works. If your report has multiple tabs, then the tabs are displayed in the blue frame at the bottom.
As for the hover help, you can adjust that by putting the right information into your URL. I don’t recall what it is, but “comments” can be added to the URL so that the right comment is displayed.
Ok Anita…
In my case when i use your good code,happen that if my personal setting in infoview for see the report are “optimized for my browser” ,i can’t see a little pop-up window,but the function work fine.
The only thing that i 'd like to change from your code is :TARGET="_BLANK" but this doesn’t work fine…
this is my code in my variable in BO full client:
I am running off to a meeting – but I believe, that for this to work, you need to switch your Infoview setting to view HTML. Try that, and see what happens.