Hi, in my experience you need wholly UNIQUE keys at every level. In your scenario week 26 for (say) 2015 is not differentiated from week 26 for any other year. What I am suggesting is generating a pseudo key for your quarters, months, weeks etc that will give uniqueness and sequentiality, you can make the display key the…

Hi, say your source report has 3 columns A,B,C that need to be prompted and various others that don't. You create a dashboard prompt for each of the three and you set variables in the dashboard prompt for each {MyVarA} {MyVarB} {MyVarC} When you click on a row of data you will see that the prompts "catch" the values you…

Hi, another poster has given you the answer to this. Create a hidden dashboard prompt that includes a prompt for the value that you want to coordinate. On that prompt have it set a variable. It is worth starting with this initially not hidden to check that it is catching the click on the data item as it should be. Use that…

I have not experienced this on your version, but I previously used session variables to refresh instead, one it makes sure your variables really are 'current' and two it consistently works and is usually not too much of an overhead.

The workaround I have used for this is to make them session variables, this also guarantees that the variables are as fresh as the user's log in.

I guess two actions from your comment, one remove the limit (for a single user) and see if it works. Two have a look at the defaults for your Hana database and see if they are all compatible with the defaults OBIEE is applying. I know less than zero about Hana database, but if it works with filters is it in any way like…

Look also for what you cannot see. i.e. check the length of the values, I have seen DB content that looked to the eye identical but was in fact padded with nulls to a fixed length! If numeric is there any spurious decimals? If text could it be character set issues?

Have you seen this => An Essbase OBIEE integration walk through with tips and tricks

Many thanks, that is what I was looking for. love the way upgrades result in functionality that worked previously n longer working as standard!

Hi Christian, but I am running it and I am not seeing physical SQL when I use; - 1. Create diagnostic sql view in the report 2. Set logging level 5 and view diagnostics log via manage sessions Is this a change in 12.2.1 that you have to use the NQCMD?! Apologies if I am being less than crystal clear. Robert.

Do you see strange ODBC errors on the front end? Have you tried shutting your service down, replacing the current rpd with the default rpd and then restarting and using your original rpd (validated in off line mode first to check it is 100% a-okay) to upload?

On run it, that is what I have been doing, having set the logging level and making sure cacheing was off, and then looking at it via diagnostics expecting too see logical and physical sql, but in fact only seeing logical sql, From you saying 'jokes aside' I assume that the original way should facilitate viewing the sql,…

Just a thought, the AGO function uses the date hierarchy in its inputs, does the user in question have rights to those, or is your date hierarchy not exposed in the presentation layer? And, is the AGO created in the rpd or in the analysis? Also, is the date in question in the same presentation subject area as the other…

Reading your response as 'No, it makes no difference if the user name attribute changes', if I understand you incorrectly kindly correct me. And thanks as ever, Robert.

Don't have colums in the analysis that are not displayed in any of the display outputs. Push compex logic back to rpd wherever possible.

The comment was not directed at you, I just wanted to point out to the asker that the syntax is dependent on the data type. No criticism intended or implied of your good self or your most detailed and salient response! :-)

Note the single speech marks in the example in Christian's reply, necessary for varchar fields....

My mistake! Thanks, Robert.

Not the news I wanted but thanks for the answer....

Have you tried it the other way, casting your literal to a datetime?