Hi, I might be misunderstanding your requirement, if so please post some brief illustrative data, but have you thought of pinning a copy of a base measure to the dimension hierarchy represented by B - "A Aggregated by B". You could create an alternative drill path for this purpose if one does not exist. Hope this helps?…

I concur with Christian, more detail please. OBIEE does not provide rollup aggregation, if your data source is a database table / view then you would need to add the additional levels as explicit column(s) in that table, then default sum aggregation behaviour on those columns will do the rest for you, and if you can put…

Hi, I would create date prompts not based on either of the two dates, one a "From", the other a "To". Use the From to set a variable VFromDate, the To, VTODate Reference the date variables on filters on your reports using >= {VFromDate}{SomeVeryEarlyDefaultDateHere} and >= {VToDate}{SomeFarFutureDefaultDateHere} on both…

Very kind. I always think that if we just do what is asked we are not doing our jobs, we should be providing the best advice we can to protect the client from bad practise and its long term and short term consequences. Now if only the askers of the questions would mark their answers ;-)

Beware of putting function logic on time measures that you then use as filters. This will have a very real impact on performance. Better is either to have the values populated in the format that you want in the data warehouse, or if that is not possible then tell the end user population to live with it, the trade off on…

Hi, the default drills will only work on real fields, not calculated ones, how would the system 'know' that formula X is the same as formula Y in another report? Ways around this; - 1. Populate a variable with your value to filter on and filter your target based on the variable 2. Have a decently designed time hierarchy…

Hi, on your slice by slice the only other point is to move your generated value to a page or prompt level. Do you still have an issue?

You need to use the substring function, in conjunction with the locate function, see below for a very similar question => Alternative for INSTR() in OBIEE

On should work - does the variable get set if you actually use the prompt and select a value and click go?

Can you repeat the test, I would try a shorter name, all upper case, no special characters, see if it makes any difference. If it doesn't make any difference I would log an SR, this is standard functionality and should work!

And did you check the scope of the variable is not restricted to page? And is your prompt coming from the same subject area as the one in the report? Can you put a text or heading on the same source page to ascertain if the variable is being set?

On your previous slide where you show the prompt I cannot see the value that you have created the prompt on, is it definitely the column that you are invoking the drill behaviour from? Also check the scope of your dashboard prompt - is it global?

Hi, it seems you have the filter as the explicit value 'pv_agreementvar' - this will never work, unless you have an agreement of that name!? When you create the filter one of the options is to use a presentation value as the equal to / in value, you need to use this and it will then pull the variable, not use the variable…

I don't currently have access to OBIEE, but there is a means of generating the links - which takes most of the work out of GO_URL, so go the target report, filter it as you need and then capture the url at that point and compare with what you have. See the below; -…

Hi, two things to check; - 1. Make your prompt visible if it is not. Click on your value that invokes the navigation, but make sure it does it in a new window - go back to the original window, did the prompt change to the value that you just clicked on? 2. On the target page add a title / text area or similar and display…

Hi Christian / Gianni, I have suffered this one a number of times so much so that it became personal policy to run the same code as the same user on the same database to avoid the blacklisting issue - and I come from DB developer background so am most at home there. I found that the dynamic variables failed so consistently…

Time dimension more than any other will impact performance if not optimal. I would generate two new pseudo keys to use for your requirement using a rank function in the ETL on the combinations of values as shown in Martin van Donselaar's post.

Hi Gianni, always happy to be corrected! I always use a single table for date hierarchies, to do otherwise is to impact performance - I have seen places use views on very large tables and then wonder why their queries always run slowly. So, given one table, and given that each row of data has to possess every key, I don't…

Hi, I don't think week is an issue, I am sure I have had this in hierarchies previously and as long as you have more weeks than months (and it would be a really strange year otherwise!) then it is fine, the granularity is the important factor, less to more is the rule. So you can have hierarchies of things that are not…

Also set up your dimension hierarchy to reflect this, total, year down to your lowest level of granularity with the chrono keys as the key for each level and all other members at the same level of granularity populated on the same tier as its key, the ago function will then use these keys in its logic.