- Introduction
- Report Readers
- Report Authors
- DevOps
-
Developers
- Quick Start
- Breaking Changes
- ActiveReports Version Compatibility and Migration
- License ActiveReports
- Configure ActiveReports Using Code
- Work with Reports using Code
- Report Parts
- Create Designer and Viewer Applications
- Extensibility in ActiveReports
- External Customizations in ActiveReports
- Export Reports
- Print Reports
- Plugins Development
- Samples
- Troubleshooting
Page/RDLX Report
Page/RDLX reports is the ActiveReports extensions of the MS RDLX specification. Developers should clearly understand the behavior of these reports because it can conflict with other requirements.
- Imagine an RDLX report as an infinite canvas (as well as a multi-section report as many canvases tied together) that can grow in two directions, depending on data. The pagination in this type of report works according to predefined RDLX rules - a page break before/after, orphaned headers/footers and other.
- A Page report is a set of predefined pages with static and dynamic data content. If data doesn’t fit to a page, the entire page (static content) is cloned and filled with new dynamic data content. A Page report has a special control - OverflowPlaceHolder, to keep place to dynamic data.
From the developer’s perspective, such difference makes sense only in case of requirements to exports or master reports because:
- Word DOCX export works well only with RDLX reports.
- Excel export in the single page mode works well only with RDLX reports.
- Excel Data export is similar to the RDLX report template.
- Master reports support only RDLX reports.
- Galley (not paginated) mode is available in RDLX reports only.
- Only RDLX reports support header/footer. Per page static content (not only on header/footer) can be implemented in Page reports.
See Also
Create a Report or Load an Existing Report
Bind a Page/RDLX Report to Data