I am receiving a single EDI file with multiple ST-SE segments and I need to split them into separate fixed-width files so that the WMS can import them. I tried following the instructions in Skip Aggregation for EDI Missing. I did look through the backend IO option and the setting for skipAggregation=true.
However, when I run my flow, it still only exports one concatenated/aggregated file. So far I've tried changing the Batch and Page Size settings on both the Export and the Import and I'm getting the same result.
How do I take one EDI file with multiple ST-SE segments and turn it into a series of smaller files in Integrator.IO?
@jackharris , I assume you're using a one-to-many setup here. Skip aggregation isn't ideal for this scenario where each ST needs to be its own file, as it only operates at the page level (i.e., it doesn’t aggregate pages). To address this, you have two options:
Set the export path to records at the ST segment level and configure the page size to 1 (though this approach may result in losing data outside of the ST segment if it's required).
Create two flows: the first flow retrieves the EDI and dumps the JSON into a file provider intermediary (e.g., NetSuite file cabinet, Google Drive, or any FP) using one-to-many, ensuring each JSON object represents the record you want to process in the next flow (or transform it beforehand) and does not have skip aggregation enabled. The second flow then processes the dumped JSON with a page size of 1 and skip aggregation.
@jackharris can you screenshot some of your setup? Are you using one-to-many on the import step pointed to ST? Then on your webhook is the page size set to 1?
@jackharris on the webhook flow, when you look at your run history, does the record count equal the page count? Also, do you have skip aggregation set on the FTP step that's on the webhok flow?
On a different note, instead of using the “webhook” from the drop down, you can just use “integrator.io” connector and then the “listener” option. Doing that makes it so you don't need to make a username/password that you have to keep up with.
