This tutorial shows how to replace non-Latin characters in XML files with the XSLT Transformation action in Advanced ETL Processor. Use it when an XML feed contains characters the receiving system cannot accept. XML is strict enough already. It does not need surprise characters joining the meeting.
What You Will Learn
- Use an XSLT Transformation action inside a package workflow.
- Apply an XSLT file to standardise XML content.
- Replace characters that cause downstream XML imports to fail.
- Review variables and execution logs after the XML transformation runs.
Before You Start
Use a test repository or safe sample data while following the tutorial. Production jobs are a poor place to experiment.
XSLT Transformation Action Docs
This tutorial uses the XSLT Transformation action to transform XML into a standard format. In this case, the transformation replaces non-Latin characters before the XML file is sent to the next step.
The XSLT Transformation docs explain what XSLT is and how XSLT is used in Advanced ETL Processor packages.
The action reference also covers the parameters tab, variables tab, execution log tab, and calculated XML file name example. The docs recommend UNC paths instead of mapped drives for automated network file work.
Related XML actions include XSD Validation Action and XSLT Transformation Action. For background, review advantages and disadvantages of working with XML, ETL and XSLT, 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.