Community
Participate
Working Groups
Current behavior - In the data binding column we support the following fields = Name, dataType, expression, aggregateOn, etc. The aggregateOn field is set only for aggregation binding columns ( i.e binding columns that refer to Total.Functions ) and other cases it is “N/A” In cross-tab report item the similar concept has been applied. As of now the aggregateOn field is only set for data binding that define an aggregation. Based on discussion between Wenbin, Gary and me, the following has been agreed. New behavior ( we need to support for BIRT 2.2 ) 1)In cross tab, the AggregateOn will also be set for non aggregation fields too. Example a) name= country, expr = level[ country ] , type=string, aggregatOn={ “Location”, “country”} ( dimensionName, levelName) b) name = state, expr=level[state], type=string, aggregateOn= { “Location”, ”state” } c) name = sales, expr = measures[“sales”], aggrgateOn=”” d) name = TotalSalesForState, expr= measure[“sales”], aggregateOn= {“location”, “state”}, function = SUM 2)Adavantages – Will make the cross tab filter and sort UI easy. Also each bound column is associated with a level. If the aggregateOn is empty, it means the bound column is for the detail row. a. Filter i. User selects the level for which he wants to define filter, In the filter condition we only list out the bound columns which have one of the aggregateOn = levelName ii. User selects the level for which he wants Example if user specifies Filter on level = Country b. SORT selects the level for which he wants to define sort, In the SORT key we list out the bound columns which are defined for that level ( i.e which have aggregateOn = “levelName” ) This will require following UI changes 1) Whenever UI adds a level and dimension, and adds bound column, it needs to make sure the aggregateOn field is set to the levelName. Please make sure all addBoundColumn calls set the aggregateOn field as agreed. 2) UI – To show the binding columns for that level in the SORT key and Filter key field list. [wenbin]: More specifically, the sort/filter key field list should show binding columns that has aggregateOn == the current level key.
Created attachment 65432 [details] suggested changes to filter and sort dialog
Created attachment 65729 [details] Updated sort and filter UI
This bug contains two changes 1) Enhancments to aggregateON field to set the correct value 2) Advanced filter and sort support.
*** Bug 184070 has been marked as a duplicate of this bug. ***
We no more need to set aggregateON field for non aggregation column bindings DtE will provide the API - get the list of column binding available for sort and filter for a given level
(In reply to comment #3) > This bug contains two changes > 1) Enhancments to aggregateON field to set the correct value > 2) Advanced filter and sort support. > We dont need to make the (1) change mentioned above.
DTE will support some API about memeber value. And the other APIs is avaliable.
Created attachment 68032 [details] xTab Filter and Sort dialog changes. Based on the comments the dialogs have been revised. In addition, window-preferences will have 'Filter limit' category under report design to change the default values.
Please make sure page # 7 in the PDF is the major change.
Aashima has updated the UI to allow user set the Filter limit using Window Preference.
I shall do the coding soon, but we need DTE to provider another APIs about member value, Chao Chen will send DTE a bug to provider an APIs.
Created attachment 68470 [details] changes in showing warning when list cannot be populated for filter expression page 8 has been added to the PDF that shows a warning when user selects a measure or aggregation and values cannot be displayed in filter condition.
Fixed.
When user select member value list(see page 6 and page 8), it may return error list or throw an exception, that's because the APIs from DTE contain error. I've sent them a bug to resolve it. (Bug 189575)
Its not complete yet, please refer to comments from Aashima
I do not see Comment #9 implemented. Having the filter limit in Windows-preferences is not fixed
Please see preference Report Design -> Crosstab, there's a page to set filter limit. I only change the page name from "Filter Limit" to "Crosstab". That's because "Filter Limit" will confuse users, what does it mean? What's you opionion ? If you still insist, I'll change it to "Filter Limit".
There're 2 relative bugs to this one. Bug 189805: assigned to Model. Bug 189807: assigned to DTE.
Another relative bug 189829, Lin will handle it.
Created attachment 69243 [details] Crosstab Preference Page The preference page in Comment #16, it's not missing.
The attachment in comment #20 is the preference page. The difference between the page and spec is the page name, and the others keep the same. Set to FIXED.
UI verified. Build id: v20070531-0630
