Summary: | BIRT Cross tab, Cube - Time dimension enhancements | ||
---|---|---|---|
Product: | z_Archived | Reporter: | Rima Kanguri <rkanguri> |
Component: | BIRT | Assignee: | Chen Chao <cchen> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | Keywords: | plan |
Version: | 2.2.0 | ||
Target Milestone: | 2.2.1 | ||
Hardware: | PC | ||
OS: | All | ||
Whiteboard: | |||
Bug Depends on: | 197589 | ||
Bug Blocks: |
Description
Rima Kanguri
2007-07-17 21:11:33 EDT
Support format property for levels of time dimension. See the following schema, each levels on a time dimension already has the actual data column as the attributes. We could add a new format property for each levels. The default format could be: level Year: “YYYY” level month: “MMM” level week: “EEE”, Cube builder should also provide the way to change the level format property using date time formatter. <tabular-dimension name="Order Date" id="177"> <property name="isTimeType">true</property> <property name="defaultHierarchy">NewTabularHierarchy2</property> <property name="hierarchies"> <tabular-hierarchy name="NewTabularHierarchy2" id="178"> <property name="levels"> <tabular-level name="year" id="179"> <property name="dataType">date-time</property> <property name="dateTimeLevelType">year</property> <property name="columnName">ORDERDATE</property> </tabular-level> <tabular-level name="quarter" id="180"> <property name="dataType">date-time</property> <property name="dateTimeLevelType">quarter</property> <property name="columnName">ORDERDATE</property> </tabular-level> <tabular-level name="month" id="181"> <property name="dataType">date-time</property> <property name="dateTimeLevelType">month</property> <property name="interval">none</property> <property name="columnName">ORDERDATE</property> </tabular-level> </property> <property name="dataSet">order_details</property> </tabular-hierarchy> </property> </tabular-dimension> Aggregation on time dimension: Fist, with BIRT 2.2 build, I seems can’t make the aggregation on time dimension work. we should look to this issue. Second, BIRT should also support the following usage scenario: - Create a crosstab that select all states that has sales > 1m in year 2003. - After seeing all states that has sales > 1M in year 2003, we want to see all cities in each of those states by show the city level on customer regions dimension. The first step works fine. However, the second step seems always fail. This seems to be a bug in BIRT 2.2. I include this in this project so that this issue will be tracked. Reassign to wait model change. Model part is fixed. Add 'DATE_TIME_FORMAT_PROP' in LevelHandle. Assign GUI to fix the left part. We need the UI mockup to edit dateTimeFormat in cube builder. To support format property in cube dimension level, we should also make the following changes in GUI: 1. when the user drag and drop a time dimension level to a crosstab, the binding expression created on the crosstab should also include the DateTime attribute. For example, if you drag and drop the [Year] of Dimension [OrderDate] to crosstab, the default binding expression should be dimension["OrderDate"]["year"]["DateTime"]. Of cause, people can change this expression as needed through expression builder. 2. GUI should also copy the format property of level [Year] to the data item just created. 3. no changes are required for DtE or Engine side for this time dimension format enhancement. please make the change in cube builder and data item format page. Fixed it. |