We currently have a whole suite of report designs that cover various parts of our app, and these reports are generated on demand by our users.
我们目前拥有一整套报告设计,涵盖了我们应用的各个部分,这些报告是我们的用户按需生成的。
I want to be able to bundle up several of these reports into a single report to return to the user.
我希望能够将其中几个报告捆绑到一个报告中以返回给用户。
I initially hacked up a custom report builder that generated report design files using segments inside a report library file, and then ran that generated design, but this was unwieldy and a pain to manage as I had to duplicate the individual reports (still required) inside the report library file. Any changes to the stand-alone reports had to be duplicated in the library for the combined reports.
我最初破解了一个自定义报表生成器,它使用报表库文件中的段生成报表设计文件,然后运行该生成的设计,但这很难处理,因为我不得不复制单个报表(仍然需要)报告库文件。对于组合报告,必须在库中复制独立报告的任何更改。
What I am really looking for is a way to specify several design files, have them all run, and then return a single file to the user, containing all the reports they selected.
我真正想要的是一种指定几个设计文件的方法,让它们全部运行,然后将单个文件返回给用户,包含他们选择的所有报告。
1 个解决方案
#1
3
This is a fairly common request, that we are working on but have not solved yet.
这是一个相当普遍的请求,我们正在努力但还没有解决。
One approach that is not ideal that you can use today is to run each report and then combine the output from each rptdocument. BIRT-exchange has an example of this here for PDF and HTML. The problem is that the page numbering will not be correct and the TOC will not be right either.
您今天可以使用的一种不理想的方法是运行每个报告,然后组合每个rptdocument的输出。 BIRT-exchange在这里有一个例子,用于PDF和HTML。问题是页面编号不正确,TOC也不正确。
The better approach is if there was a merge report engine task that would allow you to combine multiple rptdocuments into a single rptdocument with appropriate pagination and TOC. There is a bugzilla entry here that I hope to see in the 2.5 (June 2009) version of the product. If you are interested please have a look in and give your feedback.
更好的方法是,如果存在合并报告引擎任务,则允许您将多个rptdocuments组合到具有适当分页和TOC的单个rptdocument中。这里有一个bugzilla条目,我希望在2.5(2009年6月)版本的产品中看到。如果您有兴趣,请查看并提供反馈。
Finally, one of the features that I would like to see in the product for 2009 is some refinement to the DesignEngine API that allows a developer to easily compose a single report design at runtime, using components from other report designs. I have created a bugzilla to track this too.
最后,我希望在2009年的产品中看到的一个功能是对DesignEngine API的一些改进,允许开发人员使用其他报表设计中的组件在运行时轻松编写单个报表设计。我已经创建了一个bugzilla来跟踪它。
If none of these seem appropriate let me know and I will see if I can help you find a different solution.
如果这些看起来都不合适,请告诉我,我会看看是否可以帮助您找到不同的解决方案。
#1
3
This is a fairly common request, that we are working on but have not solved yet.
这是一个相当普遍的请求,我们正在努力但还没有解决。
One approach that is not ideal that you can use today is to run each report and then combine the output from each rptdocument. BIRT-exchange has an example of this here for PDF and HTML. The problem is that the page numbering will not be correct and the TOC will not be right either.
您今天可以使用的一种不理想的方法是运行每个报告,然后组合每个rptdocument的输出。 BIRT-exchange在这里有一个例子,用于PDF和HTML。问题是页面编号不正确,TOC也不正确。
The better approach is if there was a merge report engine task that would allow you to combine multiple rptdocuments into a single rptdocument with appropriate pagination and TOC. There is a bugzilla entry here that I hope to see in the 2.5 (June 2009) version of the product. If you are interested please have a look in and give your feedback.
更好的方法是,如果存在合并报告引擎任务,则允许您将多个rptdocuments组合到具有适当分页和TOC的单个rptdocument中。这里有一个bugzilla条目,我希望在2.5(2009年6月)版本的产品中看到。如果您有兴趣,请查看并提供反馈。
Finally, one of the features that I would like to see in the product for 2009 is some refinement to the DesignEngine API that allows a developer to easily compose a single report design at runtime, using components from other report designs. I have created a bugzilla to track this too.
最后,我希望在2009年的产品中看到的一个功能是对DesignEngine API的一些改进,允许开发人员使用其他报表设计中的组件在运行时轻松编写单个报表设计。我已经创建了一个bugzilla来跟踪它。
If none of these seem appropriate let me know and I will see if I can help you find a different solution.
如果这些看起来都不合适,请告诉我,我会看看是否可以帮助您找到不同的解决方案。