Advanced ETL Processor reports can accept parameters from variables and packages, which lets one report design produce multiple outputs. Part two shows how to use a loop package action to pass values into a report and save repeated report runs as PDF files.
What You Will Learn
- Define report variables so report output can change at runtime.
- Map SQL parameters to report variables.
- Pass package values into a report during a loop.
- Generate multiple PDF report files from one report definition.
Before You Start
Test the report with one parameter value before looping through many. A bad parameter inside a loop is just a small mistake with excellent distribution.
Report Parameters Docs
The Advanced ETL Processor reports documentation explains how report parameters, SQL parameters, variables, and package values fit together.
Start with Report Parameters. Reports can use variables, but the object names must match the documented naming rules for ADO, UniDAC, and BDE connections.
For SQL-driven reports, review Defining Variables, Defining SQL Parameters, and Linking SQL Parameters to variables.
When a package supplies the values, use Report Package Parameters. If string parameters are passed from a package, put the variable name in quotes as shown in the documentation.
Need Advanced ETL Processor First?
Download the Advanced ETL Processor trial before following the tutorial, or review Enterprise if you need scheduled unattended execution.