Community
Participate
Working Groups
It is quite common to have the need to run several reports and then render them all into one report. In practice, this could be achieved (from the user's point of view) by the ability to merge multiple .rptdocuments to one or IReportEngine.createRenderTask method taking an array of IReportDocuments instead of just one. This issue seems to come up frequently in the newsgroup. There is a workaround for html and pdf here: http://www.birt-exchange.com/modules/wfdownloads/singlefile.php?cid=2&lid=157 However, this does not address the issue for the other render formats. There also seems to be a code sample of how to merge rptdesigns, but I think that is a poor option - it is good to be able to run the reports separately (in my case ability to do this is mandatory) and then produce one report when rendering.
Can we get this targeted for 2.3?
there still several issues to discuss: 1. page number. Should the page number be continue among reports, if the user has ability to control the behavior. Even more, could the suer control page number of different report. 2. pagination. Should BIRT merge the first page of second report into the last page of first report. Should the user has the ability to control this behavior.
(In reply to comment #2) > 1. page number. Should the page number be continue among reports, if the user > has ability to control the behavior. Even more, could the suer control page > number of different report. IMO, there should be an option e.g. on the master page to restart page numbering. This should be possible even within a single report. If this option exists, then this would be a no-issue as the option would work the same independent of whether we are forming the report out of several rptdocuments or not. > 2. pagination. Should BIRT merge the first page of second report into the last > page of first report. Should the user has the ability to control this > behavior. IMO continuing where the last report left off should be the default behavior. If this is not what the user wants, he can set a "page-break-after" in the last element of the first rptdocument.
I agree with Antti, default is continute page number. In terms of how to break the default behavior, I don't think it should be a report level option. Instead I would recommend making it a ReportEngine Task option. Tying this option to any single report would I think be confusing. Tying it to the task makes total sense. One other option would be to make it a parameter within the ReportEngines task creation. I realize this is an API change, but it seems like we could add the following new methods fairly easily to the ReportEngine class: createRenderTask(IReportDocument) //default createRenderTask(IReportDocument[], Boolean restartPagination) // NEW createRunAndRenderTask(IReportRunnable) //default createRunAndRenderTask(IReportRunnable[], Boolean restartPagination) // NEW createRunTask(IReportRunnable) //default createRunTask(IReportRunnable[], Boolean restartPagination) // NEW I have added Jason to this, can you provide your two cents?
defer to next major milestone.
(In reply to comment #2) > there still several issues to discuss: > 1. page number. Should the page number be continue among reports, if the user > has ability to control the behavior. Even more, could the suer control page > number of different report. > 2. pagination. Should BIRT merge the first page of second report into the last > page of first report. Should the user has the ability to control this behavior. 1. Suggest to continue the page number 2. suggest NOT to merge any page. Also need to consider how to handle TOC. ALso suggest to create a new task, such as mergeTask, to take a list of report documents as input and generate a single report doc as output.
suggest to move it to future.
Schedule to future for now due to lack of time for 2.5.0
Is there any progress on this issue or is it available in 2.5? or should I use an alternative like this one at the moment? http://www.birt-exchange.org/org/devshare/designing-birt-reports/157-combine-reports/
Is there any way to use that in the current release or are there any plans to implement it in one of the next releases? Can't find anything about it.
I am also in interested in this functionality.
Me too. Is there any progress on this?
Any news on this topic ?
