Forum Discussion

alex_panganiban's avatar
alex_panganiban
Contributor
2 years ago
Solved

CSV Parsing Error, More Columns Than Data

I am experiencing a parsing error that I would like to be able to gracefully handle before the data streams into the CSV Parser snap. We receive a file from a partner where the last row doesn't actua...
  • alex_panganiban's avatar
    alex_panganiban
    2 years ago

    Hey Y'all, thank. you so much for your responses. I made a discovery of something that I wasn't aware of before asking this question. When the CSV Parser detects an error, one of the fields that is outputted in the error view is $original.record. Now that I know about this field, I can leverage it to determine which errors need to be reported and which errors may be ignored. Initially I had wanted to handle my error condition before the CSV Parser, but now I can handle it just as effectively post CSV Parser.

    Again, thanks so much for your support. I really love this facility as I know I can always count on the community to help me solve any challenge.

bojanvelevski's avatar
bojanvelevski
Valued Contributor
2 years ago
Copy Link

Hey alex_panganiban,

You can trim the record to fit the headers, which will result in additional record with the hidden character as a value for the first column, in this case "employee_id".

 

From here, use Filter snap to exclude the records that doesn't have a "first_name" for example:

!$.hasPath('first_name')

Let me know if this works for you.

Regards,

Bojan