There has a lot of talk about the OBIEE timestamp issue, and I remember a blog by Mark Rittman that suggests a cast of the retrieved date value into a DD-Mon-YYYY format as the default value in the Dashboard prompt.A Sure's a cool idea, but then I realised that when I try to constrain the values in the other prompts that accompany the date prompt, we would run into issues.
Having lived in Singapore for over 3 years now, I am tempted to use the phrase "so how?". So How? Well, the good news is there is a way out. But for those who are a little confused as to what I am talking about, here's a quickie:
You have a dashboard page in OBIEE that has a set of prompts, one of which is a reporting date field. To make it convenient for users, you would like to set the default to the most current date for which data is available. This is an easy one - assign the latest date to a variable, and default to the value of that variable. One problem though - the value is treated as data of type Timestamp, and when the reports use this value as a filter (timestamp instead of date), the Oracle DB does not use any indexes on this field causing performance issues.
Like many other things in life, the solution is very simple - in Answers, bring the reporting date field into the criteria pane, filter on the reporting date and set the value to the variable. Move to the advanced tab, copy the logical SQL and use that to default the value for the prompt in the Dashboard. The result - Magic!
Like many other things in life, the solution is very simple, but only after someone has discovered it. Watch this space out for another important tip on how to delete a catalog user. The last I saw, which wasn't a very long time ago, Kurt said we have to live with it. Now what am I talking about!!! :D
Thursday, March 25, 2010
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment