This tutorial shows how to replace non-Latin characters in file names in Advanced ETL Processor. Use file metadata and related file actions to inspect the original name, build a clean name, and move or rename the file before the next system sees it. File names are data too. Sadly, they can be just as messy as CSV columns.
What You Will Learn
- Read file metadata into package variables.
- Use clean name details when preparing a safer target file name.
- Rename or move files after non-Latin characters are handled.
- Check variables and execution logs when file-name cleanup fails.
Before You Start
Use a test repository or safe sample data while following the tutorial. Production jobs are a poor place to experiment.
File Meta Data Action Docs
This tutorial uses file metadata to help clean file names before downstream actions run. The File Meta Data action writes file details into variables, including file size, dates, owner, drive, folder, extension, and clean name.
The File Meta Data docs cover the metadata values available, parameters tab, variables tab, and execution log tab. The docs also recommend UNC paths instead of mapped drives for automated network file work.
Related file actions include Rename File Action, Move File Action, Copy File Action, Files List Action, and Replace String Action.
For troubleshooting, review debugging actions, working with variables, and related file actions.
Need Advanced ETL Processor First?
Download the Advanced ETL Processor trial before following the tutorial, or review Enterprise if you need scheduled unattended execution.