Advanced ETL Processor can pass the current filename from a package into a Transformer by storing it in a variable and using that variable during transformation. Use this when the same transformation processes many files and the filename controls routing, auditing, lookup logic, or output naming. File names are metadata. They are also where many workflows quietly hide business rules.
What You Will Learn
- Store the current package filename in a variable.
- Pass file context into the transformation layer.
- Use the filename for routing, auditing, lookup logic, or output naming.
- Check variable values and logs when dynamic file processing fails.
Before You Start
Test with at least two files that need different outcomes. A single happy-path filename proves very little, apart from the file existing, which is a low bar even for automation.
Filename Variable Docs
The main reference is Using Variables. Variables store values inside a package and let actions share context, including the current file path or filename.
Start with uses of package variables and example use cases. The docs include current-file examples such as #CurrentFile#, which is the pattern this tutorial builds on.
The variable parameter, creating variables, and setting variable sections explain how package values are created, updated, and substituted before actions run.
For file naming work, review Working with Filenames and Directories. For the transformation side, pair this page with the Transformer docs and Transformation Functions.
Need Advanced ETL Processor First?
Download the Advanced ETL Processor trial before following the tutorial, or review Enterprise if you need scheduled unattended execution.