Although I searched under this topic and found nothing, I would be surprised if no one has asked this before but here goes anyway:
Would anyone know if it’s possible to make an infoview report that has a link on one of the fields that when pressed, opens up another report that is based on information from the previous report.
Details:
I need an account number to be tied to a folder number (a big long nasty number we’d like our end users to not have to deal with at all). A click on the account number would activate another report that would use this link like a prompt.
Hope this is clear enough and apprieciate any help.
Thanks so much for the very helpful link. If I had known the term OpenDocument I definitely would have tried searching on that first.
I still have a question:
My goal is to make either a report run off of a link in the client to infoview or from one report in infoview to another by using the information in the hyperlink to skip the prompts. Are both possible?
When folks are talking about parent vs. child I’m not sure what this means. Does this refer to client (parent) to Infoview report (child)?
Thanks so much for any help you or anyone can give.
Russ – to answer one of your questions, the OpenDocument technique only works in WebI. You build the different documents in full client, however.
And for your next question – if you give some topic references, I could figure out in context what someone meant by “parent” versus “child” – but I would have to guess, based on this discussion, that folks are referring to the topmost document as the “parent”, and any document that gets invoked as a “child”.
I believe that you’ve answered both of my questions! Thank you!
So you can only invoke or “birth” a child in Webi but you have to use the full client to build the report. This makes for a somewhat slow testing process unless I’m missing something here.
In any case thanks again. While I’ve been waiting I’ve done some more searching and your posts are excellent. Very informative and helpful.
I haven’t played with it lately – is the WI0100 error a generic kind of error that it can’t display the page? If so, that means “something” is wrong.
Unfortunately, BusinessObjects may not have intended for folks to code these kinds of hyperlinks to “drill-through” reports – but clever folks out there figured out how. So, there are no helpful error messages if you don’t get it exactly correct.
How about taking a look here, where I tried to post the syntax that worked with me when I was testing it out – and I added some notes at the bottom to explain what I was doing in the different clauses.
Ignore the carriage-returns and extra spacing – it was my attempt to make the separate clauses more readable, rather than expecting one to figure out where one clause stopped and another ended. In actual practice, the clauses all rather run together.
I actually saw this post in my research and it has been very helpful but I’m still confused on a few points. Maybe it would be quicker if I showed you where I am at now:
Russ – what version of BusinessObjects / WebIntelligence are you using? Are you defining the hyperlink in a full-client report variable or in Designer, in a universe object? Do you have rights to the SDK?
I am not an “expert” in this – it’s just that when experimenting with how this works in the summer of 2002 – I found what worked for me in a full-client report variable, using BusObj 5.x, without the SDK. I later documented that syntax, for those constraints, as a common reference for that situation.
Your syntax is different - so I think that you’re experimenting with a different “flavor”, and I’m afraid I can’t help. But, if you give more detailed specifics (version / designer vs. full-client variable / SDK or non-SDK) – someone else may be able to chime in with advice.
And, are you defining this as a variable in the full-client report, or are you creating an object in Designer? If you’re doing a variable in the full-client report, I think you need to change your syntax to more closely match mine.
Is the syntax you show what you’ve actually entered into the variable, or is it the result that is displayed in WebI for that row? A trick you can do is to open the report in full-client (refresh it if it’s empty) - and then right-click on one of the hyper-links and “Copy” to the clipboard – then paste it into a text editor. Then you’ll see what is actually getting used in WebI. Is that what you’re showing in your sample?
You are correct in your assumption about what you’re seeing. The text I sent you was the link pasted into a text editor and then copied in my response.
I’m defining the varable in the Full Client report and then sending it to myself to test in Infoview.
I noticed that I have a few different field names than the ones in your list, particularly the ones that reference the Repository. I’m very curious how these work. Is it as simple as directories on the server or are there other references going on?
Russ, I seem to recall that the parameters (parms) you’re using might work when one is licensed for the SDK – I think they’re the ones I had tried at first and had to give up on.
1.) You know – the first parm after the …OpenDocument? starts with an ampersand – and I see that my first parm didn’t. Why don’t you try removing the & before sDocumentName first , and see if that makes a difference. I inferred that that &'s were to string/separate the different parms, or something to that effect.
2.) In comparing your syntax to mine, I do see other areas you need to check out.
You have sRepo=Corporate%20Documents – whereas I have sRepo=cosmo_doc, the actual name of my document domain, as seen from Supervisor. If you do not have Supervisor rights, you should check with someone who does (in Supervisor, Tools - Repository, and check for the “Name” of the Document domain in question) – because it’s highly unlikely that it’s called “Corporate Documents” (the %20 translates to the space character in ASCII).
3.) I’m not positive if you need to use the parms as I’ve spelled them or not, but I’m just not familar with some of syntax you presented. For example, if you’re using the parm sRepo, I think the sRepositoryName=Documents wouldn’t be needed, nor would the sRepositoryType=W.
I don’t even know what the sRepositoryType parm is – whereas I do know that the sTyp=R (or W) indicates that the Document Type is either aReporter=FullClient (or a WebIntelligence) document.
4.) So, I can only suggest that you try replacing your spelled-out parms with my example – and I do not know what the equivalent to &UserSubmit would be, nor why you would use it. I’d suggest removing the not-absolutely-necessary parms, and try giving it a go from there.
I do have supervisor rights but I’m afraid I wasn’t successful in making this feature work. I am still getting the W0I0100 error regardless of many different attempts.
I appreciate your help though. Maybe you know of some documentation that explains this process more thoroughly or with more examples. Your examples were great but obviously weren’t enough for me to achieve my goal.
I believe there is documentation for the SDK version – but like you, we are not licensed for the SDK, and do not have access to the documentation, nor the setup/licensing to use it.
The non-SDK version was worked out by someone who noticed what gets generated when you pick a repository document out to get refreshed in WebI. So there’s no official documentation.
I’d say – try to make your parameters match my example, and you’ll be closer to success. I think your biggest problem is that you’re mixing apples and oranges – the SDK version with the non-SDK version.
Also – I found that embedded blanks were a horrible nuisance – the %20 represents an embedded blank in your examples. Try making an example work with very short names and parms that do not include blanks at first - then see if you can get the blanks to work.
There is a section in the Designer’s guide that documents the OpenDocument function: (Defining Objects to Enhance Reports >> Linking WebIntelligence Reports in the Repository (pg 365 of the v5.1 Designer’s Guide))
This will call a webi report named t020206a and pass the value “VAUXHALL” as the prompt entitled “Make”.
We had quite a nightmare getting the syntax right, as some of the BO Knowledge Base articles conflict with each other. We also found that you do not need to use all the arguments listed in the documentation.
(BOB member since 2003-06-11)
(BOB member since 2002-06-20)
(BOB member since 2002-06-18)
(BOB member since 2003-01-07)