This tutorial shows how to process EDI messages from one folder with the Files Loop action, so each matching file can be picked up, assigned to #LoopValue#, validated, and transformed by the same workflow.
What You Will Learn
- Configure a Files Loop action for one intake folder.
- Pass the current EDI file name through #LoopValue#.
- Connect file intake with EDI validation and transformation steps.
- Review loop variables and execution logs after processing.
Before You Start
Put test EDI messages in a controlled folder first. Production inbox folders are not a good place to learn by surprise.
Files Loop Docs For One EDI Folder
The Files Loop action iterates through matching files and assigns the current file name to #LoopValue#. That makes it a practical intake step for EDI folders where every file should pass through the same validation and transformation workflow. One folder. Many files. Fewer opportunities for creative manual processing.
The Files Loop docs cover the action behaviour, metadata tab, parameters tab, N Value parameter, variables tab, and execution log tab.
For scheduled EDI processing, review resuming loop execution after failure before relying on unattended runs. Use UNC paths instead of mapped drives for network folders. For related package work, see File Loop, 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.