Page Reports vs. Web Reports vs. Library Components
Logi Report supports three types of reports, Page Report, Web Report, and Library Component. This topic introduces and compares these report types.
Each report type in Logi Report serves different reporting requirements.
- Web reports provide easier and faster report creation and design, faster report execution, streamlined customization, and interactive presentation style using the latest Web technology. Web reports also support agile development techniques such as continuous integration by allowing report templates to be updated by both Web Report Studio and Designer.
- Page reports are composed of one or more report tabs that are designed for the same or related purposes. Report developers can design, maintain, run and schedule these report tabs together or separately. Page reports are designed for paginated result sets as well as more complex reporting techniques such as pixel-perfect reporting. Page report templates can also be edited in both Page Report Studio and Designer.
- Library components or widgets, are charts, tables, crosstabs, control components, and others, that are created and edited in Designer for use in dashboards.
As a report developer, your first task with Designer is to decide what report type you need. The following compares the report types briefly.
Web reports are designed to be more efficient at runtime than page reports. They allow for most user actions to be performed in the browser rather than going back to the server for every request. For example, sorting on a column can be done in the browser. Web reports can therefore handle a much larger number of user requests than page reports on the same hardware. Moreover, when running a web report in a browser you have a user interface to view each component with local page navigation and scrollbars that are not available in a page report, and when exporting a web report to PDF or printing you can still do page numbers and page breaks the same as with a page report. See Creating Web Reports for an example of creating a web report in Designer, and Creating a Web Report the Quick Start Way and Creating a Web Report Using the Wizard for examples about creating and running web reports in Web Report Studio.
Page reports are designed to maximize product performance, avoid wasting data sources by sharing them in one page report, and manage and maintain reports more easily for the report developers. There are features that are only available in page reports such as subreports, bursting report, and complex calculations that require the use of formulas that use global variables. You can refer to Creating Page Reports for examples of creating page reports in Designer and Creating and Performing Data Analysis on Page Reports about creating and running page reports in Page Report Studio.
Library components are built specifically for use in dashboards. They are able to communicate with each other via a messaging mechanism, which makes the runtime data synchronization possible. Any data component built in a web report can also be saved as a library component, therefore a good way to create library components is to first build them in a web report and test the web report. Once a web report is working well you can save the data components in it as a library component to reuse them easily. Creating Library Components contains some library component examples. For how to use library components in dashboards, see Self-service Dashboard with Logi Report.