I guess the IFNULL isn't working because there isn't a NULL like the OP said in the title. It's just empty, nothing at all (which is not NULL), so the formula can't be executed on something which doesn't exist and that's why the IFNULL doesn't return anything.

I didn't try deploying my own style in the "old" way, but I would be surprised if it doesn't work anymore. The new theme management store a weird thing in the catalog with isn't really a custom style as it doesn't have CSS files but an XML with some properties inside. It looks more like a simple way for those who want to…

Hi, You get those messages when running the import metadata wizard, right?

My opinion is that it isn't supposed to be a big risk, mainly because the OBIEE core didn't really change (theme management? Yeah ... useless when you know how to properly customize OBIEE). So on that side little or no extra issue than .3 is expected. For the DV side ... it's newer, and as they had it for a while in OAC…

Hi, It's a bit unclear what you are trying to achieve. You mention 2 different things ... You want to open by default a tab, or do you want to hide all the others? (which of course will produce the same effect as opening the default tab). By the way, do you agree the "tabs" are the pages of the dashboard? (just to be sure…

mmajdana1 wrote:Hope I am wrong. Don't think you are ... The fact you had to use CSS to get it on screen is a good indicator that you can't do it in the export ...

Don't forget SmartView .... Being into Excel it gives you more Excel options.

So can you mark as required and close the thread? For now it's still This question is Not Answered. ( )

The patches are for the 12.2.1.4 setup, so you install FMW 12.2.1.3 and apply the patches on the 12.2.1.4 install you do.

Did you give up on this one? Did it work as expected?

Hi, Export to Excel can't translate custom CSS just because there is too much that can be done with CSS which can't be translated into Excel. So when exporting to Excel custom "browser" effects like your CSS or Javascript isn't exported as the tool has no idea of what to do with it.

You can try with table1 left outer join table2 and a condition to keep only rows where table1.column is null . That's one of the way to do it in SQL and you can do it in the LTS.

Hi, In the future you may want to consider storing the domain home outside the oracle home as it will make your life easier for upgrades. https://docs.oracle.com/middleware/1212/core/INFIN/infra_dir_structure.htm#INFIN351

There is a feature which does just that but not in a separate window, in the same one ... For every page where you check the checkbox highlighted it will wait for prompts to be filled before to execute the analysis (with a message telling the use it's waiting on prompts).

Hi, There isn't any public sample app anymore. You can either get your own http://www.oracle.com/technetwork/middleware/bi-foundation/obiee-samples-167534.html or get a cloud trial account and start an OAC instance there.

What Sherry George said. You can't "invent" the number of parameters of a function yourself: CONCAT requires 2, exactly 2 parameters. You try to use 3, can't work, so embed and extra CONCAT to first concatenate 2 pieces and then concatenate again 2 pieces and done. PS: OBIEE isn't Excel accepting as many parameters you want

Those links are at the analysis level, they can configures at the dashboard, page and analysis level. When you open the analysis in "view" mode you will also see them in general. You have a global refresh on the top-right if you click on your account name. As it's a browser you need to keep in mind there is a browser cache…

Well ... Difficult to say like that. It must definitely work, so what you have to do is to track all the things. So open the analysis, check what the server does (if it generate the query, if the query is sent to the DB, if the query is supposed to return the new records) etc. Logs right now are the best (and only way) to…

We will probably never see @3236706 again ... But it sounds like a badly configured time hierarchy with issues in the keys and that's why the YTD functions can't make a difference between months of different years.

A picture is worth a thousand words... There are other ways like disabling cache globally if you didn't want it (or don't need it), there is a setting in Enterprise Manager. You can also disable it on some sources (tables) in the physical layer in the RPD (there is a checkbox when you look at the properties for the table).