Hi Luigi, I don't think you are understanding me. For functions like AGO to work you have to have a well formed time hierarchical dimension with appropriate chronological keys at each level. Appropriate = uniquely reflecting the level of granularity of the level in question. You need to check the key that is defined as the…

Have you also checked your time hierarchy's consistency of number of elements at level? Do the number of elements increase as you go down the hierarchy from Total to detail?

Does sum(distinct qtt_answers by ID_ANSWERS_CLASS) not work for you as the basis of the first calculation? And sum(qtt_note1 by sk_question) / sum(distinct qtt_answers by ID_ANSWERS_CLASS) For the second. Note also, you may have to include the elements you are "summing by" in answers, just exclude / hide them in the…

All I can suggest from here is create a brand new dashboard prompt (don't copy the original and cut it down, start afresh) on your second page and add elements to it one at a time until you find out what is the point at which the behaviour manifests. If it manifests immediately - that is with a dashboard prompt with the…

Did you try renaming the prompt, did it work, I need closure!

On shorten the names I wonder if that also happens at runtime. It might still be worth trying, putting a prefix on the current name so they will be different no matter what length.

Okay, final try at which point I am completely out of ideas. I observe that your two prompts have exactly the same name, try saving one as a different name and then replacing the original prompt on the page with the renamed version and retest, after clearing all caches.

Now try removing the limit by, from the second prompted page, just to eliminate those as a possible cause

Ok, now I am confused. I thought your post was because you had two prompts on separate dashboard pages but you were finding that prompt on page 1 was causing the values on page 2 to change, and was setting the values on the second dashboard page to the values on the first. Can you kindly clarify, and confirm exactly what…

Are the Fiscal Month and Fiscal Year in the same dimension hierarchy? i.e. Do you have something that looks like this; - Total ¬ Fiscal Year ¬ Fiscal Quarter ¬ Fiscal Month ¬ Detail Where ¬ is shorthand for 'is the parent of' Reason I ask, your measure is Month to Date, not Fiscal Month to Date AND your error message seems…

That is what I am attempting to do. Put your dashboard prompt in edit mode. Edit the prompt that is synchronising. Check if it sets a variable value. If yes, then check the same on the 2nd page, if it sets the same value then irrespective of scope of the prompt being limited to the page, scope of the variable is not.

And question 2 - do the prompts set a variable, so could it be that the value of {My_Variable} is the thing causing the synchronised behaviour of the prompts. And to ask the obvious question, this is AFTER you change values on the first page, yes?

Hi 3195949 (do you ever think about changing that?) And looking at my post, can you tell me, when you go from tab page to tab page directly, by picking the tabs, are the prompts then setting the next page value, or are you moving from page to page using any kind of report navigation where the values on the report…

The number formats in OBIEE are set in the properties for the column in answers, and yes, it can support 2 d.p.

So often the keys are the answer when you get 'strange' behaviour....

Hi, if your time dimension and corresponding time dimension hierarchy are set up then it should be as easy as; - 1. Duplicate existing SUM measure currently not associated with a time 'level' 2. Drag the duplicated measure to (say) Year on the dimension hierarchy to get a Total by Year - which can be used at (say) month…

Note that this behaviour is probably not as a result of your prompts. Try this; - 1. Set a prompt on one of your dashboard tabs 2. Go to another tab where you think that the problem lies and refresh the report I suspect you will see that it is not effected by the dashboard prompt, unless the prompt is populating a variable…

Hi, CAL_WEEK_DESC - call me psychic but I suspect that is a descriptor field, not a key. You need to reference a key in AGO function. Might be worth a punt with CAL_WEEK_ID, but I would need to see what the corresponding dimension hierarchy looks like to comment more fully.

Check that you have chronological keys defined at each level of the time dimension hierarchy. Check that the underlying key for each level is unique at that level e.g. Year 2015 Quarter 201504 Month 201510 Week 201548 Date 20151201 Note your keys can be surrogates, the important factor is that they are each unique at that…

Guess 1 - you want only one graph but many periods - answer; go to display on the graph display and drag the period into the 'Not Displayed Area' Guess 2 - you want only the current month / selected month - answer; add a filter to your report month field and create a corresponding prompt to drive its content Guess 3 - you…