a) You're doing a DDR so you're not supposed to have that functionality.
b) Be glad you're on 7. As of 9 and in all 12c versions the tab isn't even rendered anymore. :-P
Thank you Christian ,
Please there is a way or some tricks to enforce the css of a cell based on some conditions ?
If it really HAS to be some spaghetti code rather than a model you can slap it into an opaque view in the RPD and then use all the functionalities you want. CSS is a super bad idea.
Christian already told you why and alternatives.
As you are bypassing OBIEE completely you must work without and if you want to have some different style on a cell or another your only option is to return HTML as the cell value and build the HTML as you require.
As you can imagine it's even worst than a DDR because not only you are bypassing the BI server but now you will also start to bypass the OBI output, so ... why to use OBI? At some point the question is valid.
Invest this time in getting your data into the RPD and build a normal analysis using a subject area so at least you can use all the things you pay a license for.
"As you can imagine it's even worst than a DDR because not only you are bypassing the BI server but now you will also start to bypass the OBI output"
^--- Oh and fun fact you're also bypassing any security in terms of business model filters and are constrained to the security applied to the credentials which open the connection.
The only way you can get this done is by implementing the conditional formatting yourself.
You'll need to go the the column format tab and ensure that the HTML markup checkbox is checked. You'll then need to use a CASE statement in your formula to set the background colour, font colur etc of the column dependent on your conditions. I don't have an example of code as I'm on a client site but you'll need to do something along these lines:
CASE WHEN column1 = 'ABC' THEN '<FONT COLOR="#00FF00">' || column1 || '</FONT>' ... END
where column1 is your DB column.
A word of warning! This is just pseudo code. Although what you need will be very close to this.
I do agree with Gianni & Christian, DDR reports should be avoided like the plague. They have their limited use cases though in situations where you'd want to report on data not required in your EDW for example, ETL status.
Morel if your question has been answered can you please close the thread? At the moment it's still open and marked as "Not Answered".
This way other users immediately see it highlighted as answered and the pertinent answer gets rendered in the original post so they don't have to scroll to find it.
Hi All ,
thank you for your different reponses .
Christian Berg and Gianni Ceresa thanks for your advice but I cannot modify the current RPD it has been provided by the vendor so far we are discussing if we have the right to use their RPD, that why i am obliged to use DDR .
Joel Acha thanks for your solution , let me try it and revert to you .
No he meant your SQL code has to bring back the actual HTML-encoded text
Thanks for the clarification Christian, So let me try to use HTML in my sql statement .
So you'd have to build your SQL statement for your DDR report. An example with pseudo code is:
CASE WHEN column1 = 'ABC' THEN '<FONT COLOR="#00FF00">' || column1 || '</FONT>' ... END column1name,
CASE WHEN column2 = 'ABC' THEN '<FONT COLOR="#00FF00">' || column2 || '</FONT>' ... END column2name