This tutorial shows how to process EDI messages in sub-folders with a Files Loop action, so each file can be picked up, assigned to #LoopValue#, and passed into the next EDI processing step.
What You Will Learn
- Process EDI files stored below a parent folder.
- Use Files Loop to iterate through the matching files.
- Pass the current file name through #LoopValue#.
- Resume loop execution after a failure when the workflow needs to continue safely.
Before You Start
Confirm the folder structure before building the workflow. Folder trees have a habit of becoming unofficial databases.
Files Loop Docs For EDI Sub-Folders
The Files Loop action is the right fit when an EDI workflow must process many files from a folder pattern. It assigns the current file name to #LoopValue#, so the next action can process that file directly. One file at a time. Much calmer than asking a whole folder of EDI messages to behave itself.
The Files Loop documentation covers the action behaviour, parameters tab, N Value parameter, variables tab, and execution log tab.
For unattended EDI jobs, review resuming loop execution after failure and use UNC paths instead of mapped drives for network folders. Related loop actions include File Loop and Database Loop. For troubleshooting, see 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.