Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 15 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Custom Radio buttons in obiee
Hi All,
I have a graph and two radio buttons, one is Month-To-Date and another one is Year-To-Date. Based on user specific selection the graph should change in same page.
Thanks in advance.
Comments
-
Hi,
you can do this with standard functionality using the column selectors or view selectors, depending on your exact requirement.
0 -
In addition to what Robert posted (which is the right answer) : you bought OBIEE, so at some point you do things in a OBIEE way and not what somebody put on a paper with no idea of the available tool.
You can the same functionality but it is a drop down menu and not a radio button ...
If you really need a radio button (like if your life is in danger if you don't deliver radio buttons), you can also use a dashboard prompt setting a variable and in the column formula you use the variable to switch between the 2 columns with a CASE WHEN.
0 -
Gianni Ceresa wrote:you bought OBIEE, so at some point you do things in a OBIEE way and not what somebody put on a paper with no idea of the available tool.
Which kind of sums up most "requirements" nicely. It's like buying a Ferrari and then start saying "Ok but now I want it to look like a Lamborghini, make the sound of a Maserati and while we're at it microwave my food"
0 -
If it looks like a duck, walks like a duck and quacks like a duck it may just be an over-engineered swan...
0 -
Only someone who has actually used the tool for years should be vetting requirements ... else there's no balance between "just do what the user asks" and "foist my will on the user".
0 -
I have alluded to this issue in previous posts on the forum where I expressed reservations about using jscript to deliver user requirements.
My reasons for this as I believe leaving the user with a solution that can be supported by those with core OBIEE skills is preferable to building a solution which is essentially not OBIEE and which the end user will find expensive and time consuming to maintain and which will probably require heavy rewrites come the next upgrade.
In the case where there is no graph type to fulfil the requirement without resorting to jscript the argument for this kind of customisation seems justifiable, if the business is willing to pay for the extra time to deliver.
In the case where the same functionality can be achieved through subtly different use of the end user tool, as in this case, or the requirement is trivial / cosmetic then I would say the customisation is not justifiable.
I am also a big fan of 'keep it simple stupid'...
I am sure others will disagree with my position on this.
Stupid not specifically aimed at anyone, though there was once a client who wanted all months to have 31 days for ago functionality.... and this was a client with a long history with OBIEE / Siebel analytics, so experience does obviously not necessarily equal wisdom.
So it goes.
0 -
Never underestimate the genius of simple.
^ quote me on it!
0 -
Robert Angel wrote:Stupid not specifically aimed at anyone, though there was once a client who wanted all months to have 31 days for ago functionality.... and this was a client with a long history with OBIEE / Siebel analytics, so experience does obviously not necessarily equal wisdom.
There is actually a whole data modeling subculture centered around "a year has 31 x 12 = 372 days so we can have nice AGO keys" !
0 -
So stupid formed a group, what else is new?!
0 -
It was presented at KScope in an own slot once?
0
