I some WebI Reports which used to work fine before making changes in the Univese to which it linked. But after making the changes in the corresponding universe, both in Development and Production, the reports in Production runs fine but the development versions of reports use to show an error as
Invalid Prompt Definition WIS 00005 See your Business Objects Admin.
When I searched for the error details I found something which tells that there are some issues with PROMPT present in the universe. But my Changed Universe doesnot have any Prompts in it. And when the same changes are made in both the environment how come one is working fine and the other one is not ?
I have tried to restored the universe form Production to that of Dev but with no luck. Even after restoring the Old backup copy present in the Dev is not helping us.
Please suggest how should I approach this problem.
I’m having the same error message. This is when I use some filters defined in the universe, which contain prompts. They are parsed OK in the universe designer, and work fine in full client. But there is no way to make them work in Webi. Has anyone got any idea ?
I have same error. When I am using BOXI R3. I have used prompt at universe level and it is working fine with desktop intelligence reports, but I am not able to create report in web intelligence.
the error I had was happening on 6.5 version, so it’s probably not the same in your case. i remember that I once solved problems by simply removing line breaks from the formulas. I hope this will help you.
A semi-common case where I’ve seen this occur is if I have used an object as the basis for the LoV in the prompt, and then the location of that object changes (while the reference to the object retains its old class name). So, examine the 3rd parameter to see if it references an active object. If not, update to the new location.
Example:
I had a class called “General Objects”, which had an object of “Current Datetime”, which in turn had a custom LoV set to it.
I also had an @Prompt function used in a derived table which used that object for its LoVs:
@Prompt('Enter Date to Calculate Balance:','D','General Objects\Current Datetime',Mono,Free,Persistent)
I moved this object to a “Date Values” class. While BO will automatically change the path for other objects and such, it will not update hardcode text, as is used in the @Prompt function. So, it still tried to refer to ‘General Objects\Current Datetime’, when it ought to refer to ‘Date Values\Current Datetime’. Fixed:
@Prompt('Enter Date to Calculate Balance:','D','Date Values\Current Datetime',Mono,Free,Persistent)
I’ve resolved the similar case just yesterday.
Ie. there were “Invalid Prompt Definition WIS 00005” error in rather simple report while all the integrity checks (especially objects check) passed well. This was caused by misuse of slash instead of backslash in
(BOB member since 2006-06-28)