| Summary: | Running sum for crosstab | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Tomas Greif <greif.tomas> | ||||
| Component: | BIRT | Assignee: | Birt-Data-inbox <Birt-Data-inbox> | ||||
| Status: | NEW --- | QA Contact: | weiming tang <weiming.tang> | ||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | bluesoldier, greif.tomas, weiming.tang | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Tomas Greif
(In reply to comment #0) > Build Identifier: > > Add running sum function to crosstab. User should be able to set in desinger: > - whether rows or columns should be aggregated > - partition expression (e.g. to get cummulated PL report by years) > > Reproducible: Always We already have running sum function in crosstab. But as to the two requirements, I don't quite understand. Can you give an example to show the case ? Thanks. Whenever I try to use running sum on crosstab (2.6.1) I get the following message: "Aggregation on cube measure can not be such type: "RUNNINGSUM" I will add some attachment with more detailed description. Created attachment 201968 [details]
Running sum in crosstab - aggregation orientation and partitions
Simple example of running sum aggregation in crosstab. This kind of aggregation/partitioning would be really useful in financial management (PL by months/years) or in projects performance tracking.
|