We're having issues parsing the different files from the different partners. We're receiving all the files in the same path and can't identify which file is for "X" TP, since all the files are in the same folder. When the first flow runs and tries to parse the 850, it throws an error because the rules don't apply.
We're receiving errors like this: TD is missing, sometimes an N1, etc. Every time they run, they consume the file and remove it from the FTP, even if it's not the correct TP/ISA ID.
Is there a way to identify the ISA ID from an EDI file before parsing it, add a filter, or do anything else to solve this?
As of now there isn't a great way, but there is a way. I would make 1 routing flow that parses the files as plain text, leaves the file on the server (under the advanced section), then have a lookup file step to grab the file as a blob (do not parse), then place the file in a new directory with either a new name or in a directory that tells what it is.
We do have an item in the backlog for bringing pre-parsing scripts to file provider sources so you'd be able to see the file as plain text via script prior to actually parsing through the parsing rules.
1 Like
Hi Tyler, I understand. How do you parse the file as plain text when transferring from an FTP? I don’t see that option when creating the step. Thanks for answering!
It's not super intuitive, but choose CSV, then enter some random delimiter to the column delimiter, then use the api to set a random row delimiter. At that point, the whole file parses into a single field.
You may also be able to build a new EDI definition that only goes up to the document number and then doesn't parse anything else.
1 Like
Thanks, Tyler, that put us on the right track. Regards.
