Pentaho Reporting Output
The Pentaho Reporting Output step renders a Pentaho report design file (.prpt), allowing you to generate output using a selected reporting engine type.
General
Step name
Specify the unique name of the Pentaho Reporting Output step on the canvas. You can customize the name or leave it as the default.
Report definition file (field)
Specify the field that contains the name of the .prpt file during step execution.
Output file (field)
Specify the field that contains the name (and optionally path) of the output file. If you do not specify a path, the file is created in the PDI client’s home folder (for example, /data-integration/output.pdf).
Accept file name from field?
Select to determine the report file and output file from incoming fields. If you clear this option, you must specify the report definition and output file paths/names directly.
Report definition file (static)
File path and name of the report definition file. Available only if Accept file name from field? is cleared.
Output file (static)
File path and name of the output file. Available only if Accept file name from field? is cleared.
Create parent folder
Select to create the parent folder for the output file (when you specify a full path in Output file).
Parameter name
(Optional) Name of the report parameter (if the report supports parameters) to populate from a field.
Field name
(Optional) Name of the incoming field that provides the parameter value. If you specify a field, the static input value is not used. To pass data to string arrays, separate items with tabs.
Output processor
Reporting engine used to generate the output type (for example, .pdf, .csv, .xml).
Get report parameters
Select to import parameter definitions from an existing report.
To view a sample transformation in the PDI client, open Pentaho/design-tools/data-integration/samples/transformations/Pentaho Reporting Output Example.ktr.
Metadata injection support
All fields of this step support metadata injection. You can use this step with ETL metadata injection to pass metadata to your transformation at runtime.
Last updated
Was this helpful?