Community
Participate
Working Groups
This is a attachment to the Question entitled "Aggregation Using a Secondary, Dependent Dataset Is Not Showing at Footer" in Newsportal. Please refer to initial question
Find the thread at http://www.eclipse.org/newsportal/article.php?id=32111&group=eclipse.birt#32111. Could you please attach the report design?
In current BIRT, in default state, when we insert an aggregation item into an inner table, the aggregation binding will be added to the parent table. This is incorrect, because aggregation can't work with a subquery. It will cause a error: "Invalid bound column name: Aggregation". But if we add a column binding to the inner table first, you will find the aggregation binding will be added to the inner table too when you insert an aggregation item into the inner table. This time the report is correct. I have discussed this issue with the Designer team. They agree that BIRT needs make an improvement on guiding use to create a correct aggregation report. But before that the Designer team need DTE to give a specification about which kind of aggregation is allowed. So I will reassign this bug to DTE team first. I still don't know whether this issue is the reason to cause this bug. So after the fixing, we need a feedback from the bug reporter to decide to close this bug or make further investigation. Thanks.
Need more investigation for this issue.
*** Bug 286610 has been marked as a duplicate of this bug. ***
A workaround to this problem is to create the aggreation column binding and then to move its XML section from the outer table to the nested table. It has been hard to find the problem. It would be nice if it could be solved.
