Saturday, February 27, 2010

If you have a separate development presentation server, you can use the developersprompt: (http://obiee101.blogspot.com/2008/10/obiee-developersprompt.html) for bypassing the BI servercache. If you always want to bypass the Presentation server cache add this to the instanceconfig file of the development presentation server:

Sunday, February 21, 2010

The ATR files in the OBIEE repository manage privileges on a item and provide a “readable” text for both the name and description of an object. Dan Malone of Calpoly did some basic research on how these work.

This article describe the build up of the ATR file when used for a report.

WOW: backup the files before you start to hack them, one misplaced byte can really f*&^k up your system!

Thursday, February 18, 2010

When you write large pieces of custom javascript on a report you might run into the strange problem that it works during development, you can save it without a problem, but when you reopen it in another session it doesn’t work anymore.

Most of the time this is caused by the rendering process of the report XML by the presentation server.

When obiee loads a report for the first time during a session it performs a SET XML. (like pushing the SET XML button in the advanced TAB =>

This causes your nicely formatted script which looked like this:

to look like this:

Basically it has become one long string. You might run into trouble because of comment lines starting with // in your code. This turns the rest of the string into a comment. Always encapsulate your comments as /*..comment..*/ .

An other problem might be missing semi-colon “; “. Always close your process steps with one.

Yes this trick will only work in FireFox (View | Page Style), Opera (View | Style), Konqueror(View | Use StyleSheet), Workarounds for IExplorer are widely spread on the net. Haven’t found it in Chrome Yet

Saturday, February 6, 2010

In this OTN forum discussion (http://forums.oracle.com/forums/thread.jspa?messageID=4025463&#4025463) JavaSript master Joe and OBIEE Crack Raghu show us two separate ways of making a conditional format for the grand total on a table.
Raghu’s way editing XML:
Let’s start with a basic table:
Make a Pivot:
Put it on a Compound Layout:
On the basic table add a conditional format on a random column:
Open the advanced tab:
locate the saw:condition part :

Copy and paste this into an good! XML Editor (fi Notepad ++)
Remove the condition from your bas table:
Go back to the advanced tab:
Copy and paste all XML into your XML EDITOR:
Locate the Pivot View part:
Copy you condition into the column part just below the labels between saw:totalValue and saw:displayFormats tags
Copy the XML back to OBIEE, don’t forget to press the SET XML tag:
There you go:
Although this method of Raghu is very elegant I personally prefer Joe method discussed in part 1. With XML Editing you run into the risk of loosing your stuff when make a change in your report easily, also most user won’t have access to the Advanced TAB.
Till Next Time

My Site's

Subscribe To

Followers

Disclaimer

Opinions expressed are entirely my own and do not reflect the position of my employer, Oracle or any other corporation. I'm NOT responsible for any damages in whatever form caused by the usage of the content of this blog. And Yes I'm human, so I tend to make a misstake every now and then