This tutorial shows how to use the Change Encoding action in Advanced ETL Processor. Use it when text files arrive in one character set but the next system expects another, such as UTF-8, Windows code pages, ISO encodings, or regional encodings. Encoding problems are small until a customer name turns into alphabet soup.
What You Will Learn
- Add a Change Encoding action to a package workflow.
- Choose source files and target encoding settings.
- Use the Which File and N Value parameters to limit which files are processed.
- Review variables and execution logs after conversion.
Before You Start
Use a test repository or safe sample data while following the tutorial. Production jobs are a poor place to experiment.
Change Encoding Action Docs
This tutorial uses the Change Encoding action to convert text files from one character set to another. It is useful before imports, exports, partner feeds, and old-system integrations where one side assumes every file speaks the same language. It rarely does.
The Change Encoding docs cover the supported encodings, including full Unicode, European languages, Japanese, Chinese, and Korean.
The action reference also covers the parameters tab, N Value parameter, variables tab, and execution log tab. The docs recommend UNC paths instead of mapped drives for automated network file work.
Related file actions include Copy Files Action, Move File Action, Rename File Action, and Replace String Action. For troubleshooting, review debugging actions and working with variables.
Need Advanced ETL Processor First?
Download the Advanced ETL Processor trial before following the tutorial, or review Enterprise if you need scheduled unattended execution.