Community
Participate
Working Groups
Build Identifier: M20100909-0800 Creating a "Greater than" filter based on an aggregate value directly from the cube and a "Bottom n" filter for the same group level based on a derived value on a crosstab report results in an exception. Reproducible: Always Steps to Reproduce: See attached test case based on Classic Models.
Created attachment 198441 [details] Sample report in which the problem is manifested
Created attachment 198442 [details] Exception logged by a different report with the same problem
While there are other issues with defining multiple filters on the same group level in the same crosstab, such as the inability to control the order in which they're applied (suggested enhancement there), doing so shouldn't result in an exception despite any other caveats.
This problem exists in BIRT 3.6.1
I have found a workaround until this problem is fixed. Instead of referring to the derived column in the formula for the "Bottom n" filter, reuse the formula that computes the derived column's value as the filter's formula (in the attached sample that would mean replacing 'data["HALFEXTPRICE"]' with 'data["EXTPRICE_Order/ORDERNUMBER"] / 2'). This will avoid the exception. (Though it still won't provide any control over the order in which filters are applied, which I would still suggest as an enhancement.)
Thank you for the detailed info.The bug is fixed in latest build.
