Hi Christian, my thinking was that OBIEE by default gives you a group by on any dimension attribute, so provided you could create an equivalent of count(distinct employee_id) then pulling Division, Department and the afore mentioned measure in to an analysis would provide the correct answer, or am I missing something? (-…

See -> https://docs.oracle.com/middleware/1221/biee/BIEIT/apiwebintegrate.htm#BIEIT363 Though I concur, the patch is a better fix if you can get it to work for you.

Hi Mayur, typically when you get this kind of behaviour it means that the data model either 'is wrong' or 'does not allow' what you are trying to do, depending on your perspective. If you have the physical model; Dimension 1 - Fact 1 - Dimension 2 - Fact 2 - Dimension 3 Then it is possible to create an analysis with Fact…

I keep reading your 'tag' as 'brain freeze' - the thing you get from eating ice cream too quickly...

If all else fails I am fairly sure with go_url you can decide to make print / export visible or not.

Agreed - though wholly read consistent data did worry me during the ETL window, subject area to subject area.

Didn't I say exactly that - "What I am telling you though, is your varchar2(4) is probably part of your problem, because I have observed that frequently cast puts extra characters that you did not want / anticipate"?! See also -> "The reason I asked on why put it in a varchar2(4) is that extra space may cause it to be '999…

When you drill do you drill to the analysis or to the tab page? If the latter (tab page) is there any reason you can not change it to drill to the former (analysis)?

My mistake - I missed that part - though I have used ETL in the past to move Essbase cubes into database tables in the past and found it superior in so many ways, largely thanks to OBIEE's lamentable short comings when it comes to MOLAP.

Better yet in the ETL!

Thanks for updating, your problem may help someone in the future.

You changed the setting against the connection pool also, as described in the link I posted?

Hi, use your dashboard prompt to populate a presentation variable. Put the filter on your corresponding column as YourColumn like '%'||'@{YourPresentationVariableHere}{AnyDefaultHere}' Note; this works, but may run slower than using the explicit values as any indexes will be ignored.

it isn't, that I know of, have you seen -> https://www.micheledinuzzo.it/obiee-12c-direct-database-request-configuration-nqserror-13017/ n.b. You also have the option to create an opaque view; - https://gerardnico.com/dat/obiee/obis/opaque_view

Hi, not fully following your logic here. Say I have something in the DB that is; - Num_Field of number data type I create a field in the business model layer based on this which uses case logic to turn its value 1,2,3,4,5 / 999 into some text groups stored in a varchar. I then expose this for use in the presentation layer.…

Have you tried restarting the services?

What I am telling you though, is your varchar2(4) is probably part of your problem, because I have observed that frequently cast puts extra characters that you did not want / anticipate

The reason I asked on why put it in a varchar2(4) is that extra space may cause it to be '999 ' or similar, hence I would either go for the 3 characters or I would trim it...

Thanks Gianni, I was asking about rpd datatype, but this obviously was not obvious to aPsikus...

Hi, your second cast implies that all EP_RATINGS are one digit apart from 999 - is this really the case? Also, why do you store your 3 digit number in a 4 length varchar? Why not; - CASE WHEN "WORKFORCE".""."HRDWH"."DimRating_MD"."EP_RATING" <= 5 THEN CAST("WORKFORCE".""."HRDWH"."DimRating_MD"."EP_RATING" AS CHAR(3) ELSE…