Reporting Examples
This page turns the former reporting workshop exercises into reusable example scenarios. Use them as practice projects after finishing the main chapter Reporting.
Example 1: Label printer
Scenario
Create a report that prints address labels for persons in a two-column layout.
What this example teaches
- using report columns deliberately,
- very compact band sizing,
- exact spacing and borders,
- sorting datasets for print output,
- fitting a fixed number of records on one page.
Suggested data
SALUTATION,TITLE,FIRSTNAME,LASTNAME- address lines
- optional contact role
Useful Jasper features
- multiple columns,
- rectangles or borders around each dataset,
- tight
Detailband sizing, Column Headeronly if it improves readability.
Example 2: Customer sheet
Scenario
Create a report that prints organisations together with their employees.
What this example teaches
- grouping by organisation,
- mixing header-level and detail-level information,
- repeated branding such as logo and address,
- page footer information such as current date and page number,
- translated text labels through text fields.
Suggested data
- organisation name and customer code,
- employee salutation and name,
- department,
- contact role.
Useful Jasper and ADITO features
Group HeaderandDetail,- parameters for date, address, or branding,
- predefined variables for page numbers,
- optional subreports for additional detail blocks.
Example 3: Customer sheet with histories
Scenario
Extend the customer sheet so that each employee is followed by related history entries.
What this example teaches
- deciding when groups are no longer enough,
- passing related data through subreports,
- filtering subreport data correctly,
- keeping complex report layouts maintainable.
Useful features
- subreports,
- subreport parameters,
- nested subreports only if the structure truly requires them.
Recommendation
Build the examples in this order:
- Label printer
- Customer sheet
- Customer sheet with histories
That progression mirrors the increase in reporting complexity from layout-focused to data-relationship-focused documents.