| Summary: | [Crosstab improvements] BIRT cross tab - Horizontal page break support OR section support | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Rima Kanguri <rkanguri> |
| Component: | BIRT | Assignee: | Zhiqiang Qian <zqian> |
| Status: | VERIFIED FIXED | QA Contact: | Tianli Zhang <tzhang> |
| Severity: | normal | ||
| Priority: | P3 | CC: | christophe.garabedian, contact, dmichonneau, lzhu, rkanguri, rlu, vinod.sreeharshan, wenfeng.fwd, whe, wyan, xxue, yli, zqian |
| Version: | 2.2.0 | Keywords: | plan |
| Target Milestone: | 2.5.0 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | Autoed | ||
|
Description
Rima Kanguri
defer to future release as discussed. An alternative solution is to support a section axis in Xtab in addition to row and column axis. Section in Xtab could be similar to section grouping table, where user can pick a cube level as the section key. for each element in this cube level, we will create one Xtab section. With this section concept, we can then allow user to set page break per section. Also allow user to set section headers. We shall also allow user to define the element count per section. By default the count is 1. For example, if user pick the city level as the section key, we will have one city in each section. If the count is 10, then we will have 10 city in each section. I think this approach might be more useful than setting horizontal page break on crosstab. Because, user might want to break up the crosstab to fit the page width, but not necessary create a new page. For example, two sections could fit into the same page. A new page will be created only if the 2nd section can not fit into the same page below the first section vertically. I suggest take the section idea instead of horizontal page break in next release. Do we want to remove horizontal page break from model in 2.2 to avoid comptaibility issue? schedule to 2.2 RC0 for this model change. Once model change is done, please change it back to future release. I think we can't remove this property separately for column levels from model, but we need to remove the column area page break setting page in UI. The page break is in levelView. Whether it is horizontal or vertical is depends on where the level is. So, UI should hide this property when the level is in horizontal direction. Got it. If user moves the level that has page break property from row to col, we do not observe it now, correct? I agree that we can not remove it from model, since user can move the level back from col to row, and we want to recover the page break setting. Since we have not decided what to do in this area, I suggest we do not change anything, and only document that horizontal page break is not yet supported. Sounds like we might need to support BOTH horizontal page break AND Crosstab Section in next release. (In reply to comment #2) Use cases like the following still need horizontal page break right? - Assume User adds year->month dimension to the column area and Products to row area. - Assume he wants to set a horizonatal page break after every 6 member in month level. He could achieve this by setting page break on the "month" level, interval = 6 I am not sure how he can achieve the above using section page break. (In reply to comment #6) > (In reply to comment #2) > Use cases like the following still need horizontal page break right? > - Assume User adds year->month dimension to the column area and Products to > row area. > - Assume he wants to set a horizonatal page break after every 6 member in month > level. He could achieve this by setting page break on the "month" level, > interval = 6 > I am not sure how he can achieve the above using section page break. I was proposing that the section key will be year-->month level with the section element count/interval to be 6. Each Xtab section will then have 6 month in the column. Horizontal page break could be an alternative, but the disadvantage of using page break is that we can not have two crosstab (each have 6 month worth of columns) on the same page. horizontal page break is supported now. Defer this bug to future release for the section feature. Move to future until get more feedback about the section support. Mark this enhancement resolved since it is about horizontal pagebreak, which is supported in 2.5.0. So that the status of this feature is current when a user search for it in bugzilla. See #210328 to track section/page dimension. https://bugs.eclipse.org/bugs/show_bug.cgi?id=210328 Horizontal page break for crosstab has been supported already, mark the bug as verified. |