AGO bug on OBIEE 10.3.1.2 – very annoying
Using aggregate tables produce incorrect Year-to-date at the lowest levels.
February 2, 2009When using Conditional Formatting in Answers I was unable to refer to repo vars
February 5, 2009There’s a bug in OBIEE 10.3.1.2 that renders time-series OBIEE function AGO useless if you’re using Filter on Logical Table Source (Content – WHERE). Apparently, the query generating AGO doesn’t pick it up and as a result – you will not see correct report. It might affect you in many ways if you’re using the LTS filters. The fix that Oracle suggested was to upgrade to 10.3.1.4, however, it’s not possible at the moment. We’ve created database views applying necessary filters there. Performance-wise we got a hit, but our business intelligence server is showing correct data.
