OBIEE Dashboard Prompt Variable

[Deleted User]

To answer that you'd have to explain much more in detail what you are trying to achieve and how and why you chose that how so far

KashSidd

Thank you and here it is:

Primary Plan prompt has SQL embedded in it as follows:

I would like the above to limit data by the following prompt which has the variable "var_career_level" as shown below:

Thanks in advance!

KashSidd

Just to clarify that it works fine when I remove the apply button but then everything within the Dashboard refreshes while you are updating any of the prompts

Gianni Ceresa

Almost every week there is this topic coming back again and again here in the forum: people want one prompt to be used to limit values of a second prompt.

Why don't you just use the "limit values by" option in the prompt and get rid of the LSQL block?

I always believe that when using LSQL based filters it's because the model isn't adapted to the business need or the values will be available in the same model and with the right links to allow the out of the box functionality "limit values by" to work. And often people end up with a LSQL prompt for nothing ...

(Of course not seeing the whole LSQL query and not knowing which model the first column come from doesn't allow to point to a direct solution)

KashSidd

lol... I wish that analogy resolves the issue but it doesnt... Offcourse, I didnt want to be in this situation either and wish it was otherwise but unfortunately it is what it is... But I do wonder why OBIEE application design have the "Limit Values By" option but not with SQL Block? This is purely lackluster OBIEE application design and specially when as you mentioned "Almost every week there is this topic coming back again and again..."

Anyways, I found a Javascript that takes away the "Apply Buttons" and now somehow I have to modify it to force the "Level" Prompt control to pass its values upon leaving that control. So when the User clicks on "Primary Plan" the values are already in the variable to be used

Gianni Ceresa

The problem with a LSQL based prompt is that you could be on a different subject area and do any kind of logic on whatever column you want. the "limits values by" requires to know exactly on which column of the subject area you work so it can find how that column impact (filter) the other column.

This limitation makes more sense after you spent some time looking at how things in OBIEE are done and work and how the RPD reference things etc.

The good thing (it doesn't help you at all, but still...) is that you aren't alone: as said almost once per week the question is posted, so many looks for the same thing and there isn't a universal solution (or it would be posted back all the time).

PS: beware playing with JS on prompts, they have tons of triggers connected and they fire lot of actions when you touch them in the UI, so your JS must not lose or destroy that.

[Deleted User]

Gianni Ceresa wrote:This limitation makes more sense after you spent some time looking at how things in OBIEE are done and work and how the RPD reference things etc.

Amen! Like driving a Formula 1 car without knowing how it works....you'll just destroy it

KashSidd

Good call!

Aspirer1234

Hi

Did u resolve ur issue? I am also facing the same issue...pls share me the steps u followed

[Deleted User]

....He unticked the "Show Apply" button...