Add a text block to your dashboard and just print out the value of the variable with @{variable-name} . To see it in a log you would need to pass it to an analysis as parameter etc. would be longer and more complex than just display it. The same work if you add a text view in your analysis itself.

3822729 wrote:Currently, anyone who is authenticated is able to get in . How is that possible? If a user isn't member of a group, it doesn't get any valid application role and therefore it must not be able to access. Did you cut the inheritance to "authenticated users", did you? Because any user with a valid login/password…

There are many ways to get there, one is what Robert posted above. You can also look in the dashboard properties and check the checkbox "Prompt before opening" for that page (as posted in the thread linked above).

Hi, If this is a table view, the order or columns isn't dynamic, it's fixed based on the order the columns are places into the table view. Only the rows could be sorted in a different way. More in general you seem to be wanting to sort based on the value of a total row, if that's the total OBIEE does calculate…

Double post with DAC - stopping Queued or Runnable Execution Plans already in the Current Runs You maybe want to close this thread and only keep open the one in the right space (the other one), and remember double posting is against this forum rules.

I'm totally with you on the fact that a move back to 11g isn't a solution to a failed move to 12c. He said he has "certain reasons", not giving a single one. This sounds like somebody somewhere decided that, and we can't do much against "smart people" knowing better. Of course they better try to solve the "certain reasons"…

Of course you could try by copying the XML around between the versions, but you could have unsupported XML not allowed by the 11g XSD or things which are allowed but not working in that way. So any automated approach could take you long to compare and debug. Being such a small environment in 1-2 days you must be done by…

1877648 wrote:Can you please suggest the best approach to execute this task? Take a workstation with 2 screens, open the 12c OBIEE on one screen, open the 11g OBIEE in the second screen. Start recreating every single object by hand, one by one. 5 dashboard, 40 analysis (a report is a BI Publisher report, I doubt you have…

I guess I saw something similar in MOS, there are a bunch of docs about export to Excel, worth having a look.

3003431 wrote:is there any permanent solution to this? Filter your dataset Ok, more seriously, you aren't having an OBIEE issue. ORA-01652: unable to extend temp segment by 128 in tablespace TEMP This is a database message, you are short in tablespace in your DB, you need to ask your DBA to look into it to either extend…

Actually a quick correction: the custom number format (https://docs.oracle.com/cd/E29542_01/bi.1111/e10544/format.htm#BIEUG13084 ) use the 3rd parameter for NULLs, not 0. Therefore you need to adapt the formula to translate 0 into NULLs first if you want it to match the 3rd parameter of the custom number format.

If you look at the help in the column properties where you can set the formal, you see the syntax to be used. It's a typical <positive number format>;<negative number format>;<zero/null format> You can't set a custom format for a not existing value, so if your cell is empty and not NULL, the format will not apply.

Everything Christian said ... If you don't care more than that in finding why and fixing things, you can set limits at the user / application role in the RPD: Manage > Identity, pick who you want to set limits Permissions > Query Limits.

3257177 wrote:But I am sure formula is correct. 3257177 wrote:...but for previous Month MTD and previous year same month MTD is not working as expected. You are sure it is correct and you say it isn't working "as expected", but still you don't want to post the exact formulas you are using for the 3 cases...

So 29 Feb 2016 will never exist in your results as well as 29-31 Jan 2017. Define the full logic with the business first, covering all these weird cases first. Clearly challenging them on their decision, the technical solution for that logic could change based on the answers ...

Assuming you are talking about BI Publisher 11.1.1.9: https://docs.oracle.com/middleware/11119/bip/BIPAD/data_sources.htm#jdbc_ds

Publisher can't come with all the exist JDBC connections out of the box, just because there is a huge number of JDBC drivers for various random sources. But Publisher is supposed to be able to use your JDBC as long as it is a standard JDBC once you configure it properly, that's why the doc explain where to copy files and…

OrientDB seems to have a JDBC driver, BI Publisher can use your own JDBC drivers, you just need to connect the pieces together. Look at the BI Publisher doc on where to put the JDBC driver files and how to configure it. To get the JDBC for OrientDB you need to get it by yourself or ask them.

As a side question, let's say current date = 28 Feb 2017 What is your PMTD and PYMTD ? (keep in mind 2016 was a leap year, 29.02.2016 was a thing) Because the answer to your questions first depend on the business rules behind these things.

Not a problem and welcome Just post everything you have, even what seems obvious or useless to you (hiding sensible information like names etc.).