I'm not sure you can do this unless you create the column in your repository with the CASE statement and name the column accordingly.
Sent from my iPhone
NO. You're filtering the expression. Not an actual column. Fitlers have nothing to do with any of the front-end playing options. They're data- and logic-oriented.
I think there is a way to do this -- but to do it, you must:
(1) Populate a presentation variable with your prompt
(2) Use a Narrative view instead of the Filters view
So, make your Location prompt into a variable prompt that populates a presentation variable named something like vLoc.
Then in the Narrative section of the Narrative view, put something like this:
(be sure to set the 'Rows to display' to 1)
I think that will give you what you want.
Well....yes....but... you're not actually showing what you're filtering. You're basically lying because you are not filtering on something called "Location" but a formula.
That's the whole reason why all this front-end cheating is just that: front-end cheating rather than proper development.
Hi to All you People that replied ....
Thanks so much for taking the time to reply to my question. I really appreciate it.
It looks as if I can't do it easily. It seems a strange omission of Answers.
So to Chris Arnold - would your suggestion allow the user to enter a value at run time in the Filter prompt
and then the report would use that as search criteria ? Christian Berg seems to suggest that wouldn't work,
or did I misunderstand Christian's reply to your suggestion ?
It will works but it's not really leveraging the standard functionalities of the tool and it can be misleading. If you really HAVE to have that logic then I would put it into an RPD column so that each and every usage is always the same and you don't have to repeat the logic (code!) multiple times.
Sure. And what about other tools accessing the metadata layer and not the presentation server?
SmartView, ODBC, web service,....
It's good that this functionalit is finally there but it is in no way a substitution for proper RPD modelling.
Taken the above pointa you can immediately add multilingualism as a probl factor. That translation is by the BI server.
Long story short. RPD column
Unfortunately we're still using OBIEE 11 so looks like I won't be able to use the Save As, but useful to
know for the future.
It looks like it would be better to create this in the repository as everyone here seems to agree.
Thanks to all for your time, and useful discussion.
Ok thanks for the update. Can you please close the thread?