The Pentaho Report Designer (PRD) is a desktop application that provides a visual design environment to create report definitions. The report definitions can be executed and saved locally via PRD or published to a Pentaho BI Server
to allow many people to access and schedule report execution. PRD is geared towards experienced and power users, who are
familiar with the concepts and data-sources used.
Recent News and Releases
- 2010-06-14 Stable builds of Pentaho reporting 3.6.1 released. more info.
- 2010-06-14 Pentaho Report Designer 3.6.1-stable: download now.
Stable
Report Designer 3.6.1 stable This is a bug fix release and supports BI Platform 3.6.
Major changes for 3.6.1, for a complete list see the
Release Notes.
Bug Fixes
[PRD-2587] - Html-content in the table-datasource breaks the table-editor with a ClassCastException
[PRD-2642] - Fit to page width and Fit to page do not work
[PRD-2656] - When previewing a report that contains parameters in the Report Wizard, the parameter panel is no longer displays.
[PRD-2657] - After morphing a string-field element created using a paste to a label element, an NPE occurs when previewing the report.
[PRD-2659] - MessageFormatParseError when editing a SampleData data source
[PRD-2661] - prerpoc.prpt example in PRD does not work, produces an error
[PRD-2676] - ${..} parametrization is broken for OLAP4J datasources
[PRD-2680] - Unable to define default report format via the publish process from Report Designer
[PRD-2684] - Unable to set a default value for time type parameters.
[PRD-2696] - Elements and bands cannot be serialized due to a bug in ElementStyleSheet.
[PRD-2697] - Attribute: Query-Limit has no effect.
[PRD-2699] - Parameter-Editor does not display the current values for Query, Id-Column or Display-Value-Column if the query was not found or invalid
[PRD-2709] - Banded subreports with pagebreaks before and after that are invisible still create a empty page
[PRD-2710] - Hiding a banded subreport creates content and possibly a empty page when pagebreaks are active
[PRD-2713] - Specifying a invalid column name in a database driven parameter must not crash - return <null> instead to follow the behaviour of the reporting engine in other places
[PRD-2716] - publishing the report with space in Report Name
[PRD-2717] - CsvTextFunction doesn't correctly process the quote in evaluate function
[PRD-2731] - Mondrian queries with parameters are executed 2 times - one with null parameters and another with the correct ones for parameters that come from formulas
New Features
[PRD-2776] - As a user, I want to be able to convert wizard reports into normal reports for advanced editing