Community
Participate
Working Groups
In a report with group, when the output is exported to excel, the groups should all be put on a separate worksheet. the report developer should be presented with a property in the excel export window.
It is a feature rather than a bug.
There are many problem in this proposal: 1. XLS file only supported limited sheets. So if the group count is greater than the maximum sheets, the following group will be ignore. 2. It is hard for the user to define which group should start a new sheet if the design contains multiple level groups. It is more complex if the design contains nested listing and each listing has multiple level groups. A simple proposal is to enhance the XLS supporting page-break mode. In this mode, each page will be outputted into one sheet. The user can define page-break on the group and output the XSL in page enabled mode.
suggest to defer to future
I think page break approach is more general than group. So the suggestion is to add an option for Excel emitter to output each page on a new sheet. Please note that the options is for Excel emitter's render task option, not an setting on the report design.
Creating a new Excel Sheet for each page on the report will only be useful when the developer has chosen to page-break at a logical point such as a new group, Table etc. The problem is that for many (most?) reports, page breaks tend to happen based on the trying to keep the page to a reasonable length or have it fit on paper. In these cases, the page break is going to happen in the middle of a group of data -- which a user would not want split across multiple sheets. From a usage scenario point of view, users typically want to export to Excel in order to further analyse the data. In this case, we need to ensure that the data they want to analyse is all on the same sheet. (As an additional comment, creating a new Excel sheet based on the report page would also very quickly create too many Excel sheets in the resultant Excel file). If we were to do this feature, likely places someone would want to create a new sheet would be: - On a new report item such as a new Table, Chart, etc. - On a new Group In both these cases, related data would be kept together on the same sheet for analysis, which is what the user would be looking for. The first one is more feasible from an automated perspective since it's unlikely that the report has so many high level report items that it exceeds the number of Sheets Excel supports (or is usable). The second one falls into the original concern highlighted in this Bugzilla -- it's likely we could have too many sheets. On a report by report basis, it will vary how many groups there are likely to be - so this may be best implemented as a property under the report developer's control.
It is a good suggestion, we need only create new sheet for the logical page-break defined by the user.
How do we address the issue that user might want new sheet on some page break, but not on other page breaks?
