on 10-06-2014 3:34 PM
I found multiple documents on how to implement this. There are mainly two versions: 1) specify the variable in BEx Query Designer or 2) specify in the analytic authorization.
What are the use cases for these two options?
IMHO it would be better to make this transparent to the query designers so that they just work with regular variables and specify the CE in the analytic authorization only.
Any ideas? Thanks in advance!
Dear Justin,
In both the cases it mandates that the variables are provided at Bex level.
For eg if you are using the second method ie CE in Analytic auth, the same variable needs to be used in the bex level also
So you cannot mention one variable in bex and another in the auth analytic.
Regards
Gajesh
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 help!
Let me just write down how I understand this concept from your answer:
In general, I will specify the CE in both, analytic auth (for instance as value auth $_cevar1) and in the query (cevar1). However, the analytic auth will not trigger the CE code, only the variable in the query.
The analytic auth value $_cevar1 just says "allow every value that is submitted to this customer exit variable".
If so, this would give me three options for the analytic authorizations:
Is this correct?
User | Count |
---|---|
87 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.