Well ... Not sure how do you want to use a CASE STATEMENT for that as it's row by row ... So it's more something you can achieve by filtering your analysis ... Like if you add filter on YEAR = 2016 and MONTH IN (Jan, Feb, Mar, Apr) and you don't add the "Month" column in the analysis you end up with April YTD figures, but…

Hi, Without a time hierarchy in your business model forget the OBIEE timeseries functions, they can't work. You can simulate the same result by modelling things differently to generate a YTD or things like that. So the question is more : why don't you want to tag a dimension as time? It makes no sense to talk about…

Did you remove authenticated user from BI Consumer app role? And why do you keep the default roles if you don't use them? As said this morning: setup your security correctly! If you don't use at all the default app roles and you defined all your owns then delete them (mainly if you don't look inside to see which one…

Hi, I have the feeling you just have a problem with your logic .... It makes a lot of AND and not a single empty / default value managed. If your presentation variable don't have a value they actually match only the rows of your tables where the values are empty, and all the conditions are linked together by AND, so it's…

Please avoid double posting ! Restrict LDAP users and shld allow only if user exists in external database tables obiee11g (actually maybe triple posting with Needs to allow login to the LDAP users, only if he exist in external database tables in obiee11g )

Look at the link rmoff posted

Chris Arnold wrote:Unfortunately, the above does not work. I get an error.This also returns an error. First would be easier if you also post the errors you get as it avoid people to guess it .... Going back to your filter: upper("Location"."Address") IN (upper(@{vAddress})) Did you try adding ' ' all around @{vAddress} ?…

Take what Thomas did, use a pivot view instead of table, add months as columns and keep years as rows => done

I would say Thomas already said most of it ... Your source isn't the best you can have, mixed granularity in a single table is the worse to use in an analytical tool like OBIEE generating queries on the fly if you don't model it right. So following Thomas advice you must model splitting the multiple granularity into…

+1 Christian But you can still edit the table opening it from the bottom-left part of your result tab screen where you have the list of all the views included in your analysis.

Hi, Just click on "Define Parameters" in your action link and set the parameter pointing to your column.

Try to replace DateNumber with CAST(DateNumber as VARCHAR(8)) or something like that making this number a varchar ...

You must manage the null : like adding a CASE WHEN all around to not execute that formula if any of the parameters are null, or manage it by setting a default value if null.

What is the type of your columns DateNumber, age and birth_date ? (the OBIEE type) And can these columns be null ?

Will not looks nice but ... Try with something like: TIMESTAMPDIFF(SQL_TSI_MONTH, TIMESTAMPADD( SQL_TSI_DAY, 1 - DAYOFMONTH(birth_date), TIMESTAMPADD(SQL_TSI_YEAR, age, birth_date) ) , TO_DATETIME(DateNumber,'YYYYMMDD') ) I imagine it will return only integers but in case you end up with a number with a decimal part add a…

Why do you want to keep it constrained with "All Prompts" ? Just select manually all the columns except for the 2 Top n giving you problems .... Or change the Top n prompts to be variables problems and not column based (this is just the value of "n" and not the value of the column itself, so a variable prompt would be fine…

Did you test the pieces of the formula independently starting by the one returning you the last day of the month? What is "DateNumber"? Is it a sysdate or something like that? Don't you have a real date next to it instead of having to transform your number in a date? The formula you wrote here has no chance to give you…

Hi, TRUNC = FLOOR : your trunc is to remove the decimal part of the number, so FLOOR is going to do the same thing MONTHS_BETWEEN = TIMESTAMPDIFF(SQL_TSI_MONTH, <date1>, <date2>) And I'm almost sure that your translation of LAST_DAY isn't returning you the right value .... To get the last day of a date in OBIEE you are…

On a 32bit Office 2013 it works (I have it in front of my eyes), that's for sure

Well .... I must admit I never test it on an Office 2016, but also on Office 64bit. And not sure which one (if not both) could be a problem ... Would be great if somebody else here around used it on Office 2016 or on an Office 64bit and can post a feedback.