The Files Loop Action iterates through a list of files and assigns the current file name to the #LoopValue# variable. That lets one tested package action handle many files without cloning the same step until the screen looks like a filing cabinet accident.
What You Will Learn
- Use Files Loop Action to iterate through matching files.
- Pass the current file name through the #LoopValue# variable.
- Control which files are selected with file age, count, and size parameters.
- Resume loop execution after failure when processing must continue safely.
Before You Start
Use a test folder first. File loops are very efficient at repeating mistakes across an entire directory.
Files Loop Action Docs For File Processing
The Files Loop Action iterates through a list of files and stores the current file name in #LoopValue#. Downstream package actions can then read, move, transform, or load the file currently being processed.
The documentation explains the metadata, parameters, variables, execution log, and resume behaviour. The N Value parameter changes meaning depending on the selected file rule, such as files older than N days, first N found files, or files bigger than N bytes.
For network folders, use UNC paths instead of mapped drives. Mapped drives often disappear when a package runs under a service account, which is Windows politely saying it has never heard of your Z drive.
Need Advanced ETL Processor First?
Download the Advanced ETL Processor trial before following the tutorial, or review Enterprise if you need scheduled unattended execution.