on 08-01-2008 10:30 AM
I just noticed XiR2 (Sp4) DESKI is not "remembering" what context your report is using!
Normally (at least that is what I experienced with version 5.1.6) you get the Choose-a-Context window when you EXECUTE the query, when you just REFRESH it (icon at the top) it uses the context which you had choosen when you last executed the report
Now with XiR2 it ALWAYS shows the Choose-a-Context window ...even when you just refresh it....
Can this be solved? So it uses the context which is last used when executed? (is there something like a "Reset contexts on refresh" which we have in Webi documents)
I believe for XiR2 you will be automatically prompted for a context by default.
To preven this you can set Deny for "Always regenerate SQL" for Desktop Intelligence user/group in CMC.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for your reply Ajay,
but I found " Auto_update_SQL " instead under parameter option. The option you mentioned states that its related to object securirty vs the user profile. This is what I found
Description:
Determines what happens when an object in a query is not available to a user profile.
If set to Yes, : Query is updated and the object is removed from the query.
If set to NO : Object is kept in the query.
My issue is that the user selected objects exists in the 2 contexts defined in the universe and its ok to get the results from any of the context.
And I would like that BO to either remember the context i chose for the first time it asks me or I need the option that can be set (Universe, CMC, Deski etc) that would supress the 'select context' window.
-Kavitha.
Kavitha,
The syntax is very important, it MUST be all caps. This option is applied at a Universe level, no matter what tools is using this tool. The option forces the update of SQL being generated prior to execution against reporting db. If you have other row-level security it will also update based on that. You can NOT choose when to apply or when not to apply, it applies globally always. If the object not longer exist in Universe it will remove it because it updates the SQL based the Universe being used.
Regards,
Ajay
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.