I stand by ridiculous - take 28 February, does it join to 31 March or 28th March or 28,29,30,31 March?? What is anyone trying to achieve with this, comparing 'like' with 'like', if so you have already failed as March has 31 days - February usually 28, so you would have to abandon the month and have the standard month…

If you want any help at all here then you need to clearly define your entire requirement before posting. And see my second suggestion, you could use a combination of a case statement to catch your stupid dates and filter to achieve exactly what you are after. And no I won't write it for you, and yes I do think you will…

- I have had clients insist in all seriousness on all months having 31 days! Maybe the next psychic requirement is a decimal month?! Those of you who are psychic - raise my hand?

This is the part where you use your initiative and change the "Revenue"."H0 Time"."Month" to "Revenue"."H0 Time"."Detail" - note I cannot see your revenue time hierarchy, but you need to reference the hierarchy level that corresponds to day... If there is not such a level in your time hierarchy that corresponds to dates…

Hello sweetie, you don't use AGO like that the syntax is as shown below and notice the SH.TimedDim."Month" that is just the hierarchy 'grain' from your time dimension.

"Penny" dropped. It makes sense now. Not sure how it is useful to me yet, but you never know!!!!! Thank you.

Thank you both for your very useful answers - extremely kind - I will try to push the requirement to the DW team, I agree it makes most sense there, even though as you both say it can be done - I completely agree it should not be done in my case.

Hi, I also found out through painful experience that if you have a column of width 10 (random number here) and you have text that does not break with a space in the column of width 15, then your column will wind up being width 15 - OBIEE will not break the text at your chosen width.

As one recent Newbie to another, do do the following; - Search the forum for your issue first, a lot of people have asked a lot of questions, yours may just be one of them Do provide exact version of OBIEE Do change your default display name, a lot of people ignore newbies Do provide comprehensive concise detail of your…

Amen to that. If I want a lot of sound and fury signifying nothing I will consult an end user. If I want the objective reality I will look at the data.

Thanks for translating what was being asked for!!

The row numbers are entirely 'yours', they come from whatever you populate in the case statement. Or do I not understand you correctly?!

Or case rowcount('Dummy_report_for_view') when 1 when 2 when 3 when 3 when 4 when 5 ....

Clear? No! Screenshot please?

"You first need to upgrade" - well doesn't that depend on your migration strategy, re-implement might be no more work and a cleaner solution...

People are still using 10g?! OHS is part and parcel of fusion middleware, so yes 11.whateverVersion and OHS is what you get. Why would you not migrate to 12c, do you like not being supported? And why would you try to put a Frankenstein solution in, what does IHS give you that Oracle does not?

Thanks I used a combination of your ideas and it works beautifully. Liking the master slave that is very useful. Master detail, sorry, must have been thinking about the weekend

'Vampire'? A vampire has the appearance of life but is really dead, and if you go to close then it sucks your vitality - yes - perfect fit for writeback!

Sorry! I was just curious! I agree writeback is not fit for purpose.

Are you following this; - http://ids-sol.co.uk/2017/10/24/obiee-writeback-with-dropdown-field/