Custom Excel Sheet Naming via Dependent Parameter

To set a custom Excel sheet name dynamically, you must utilize the `:sheet_name` anchor. Although this anchor can be configured as a visible parameter, you can easily hide it by assigning a negative value to its display sequence. To make the sheet name dependent on the ‘Operating Unit’ parameter, you should define a default value using the `:$flex$.parameter_name` token notation. For instance, the default value could be set as `:$flex$.operating_unit||’ suppliers’` to concatenate the selected operating unit value with the word ‘suppliers’ for the sheet name.

The `:sheet_name` mechanism is managed through the parameter definition itself and does not require injection into the main report SQL like the `n=n` or `&lexical` anchors. The parameter definition identifies the `:sheet_name` anchor, and the corresponding default value you define is used to set the name of the Excel data sheet when the report runs. By default, if this parameter is not used, the Excel output’s data sheet name is simply the same as the report name.

The final output filename that is downloaded to the client desktop is controlled separately in the Report Options section under the field ‘Output Filename’. In this field, you can define a naming convention that utilizes tokens to dynamically generate the name. Useful tokens include “, “, “, and parameterized values like “ or formatted dates using “. If you use the token “, all spaces are automatically replaced with underscores.

You can specify a secondary location to save a copy of the report output file in the ‘Additional Out. Directory on DB Server’ field under Report Options. This functionality is typically restricted to users with Developer access. The list of available directories is fetched from the `dba_directories` table, and similar to the Output Filename, tokens can be used here to create a dynamic path based on runtime parameter values.

By default, if a scheduled Blitz Report retrieves zero rows, the system will suppress the delivery of an empty output file when using Oracle standard concurrent delivery options. If your business requirement dictates that empty files *must* be sent for scheduled reports, you need to change the profile option ‘Blitz Report Suppress Empty File Delivery’ and set its value to ‘No’.