Has anyone else noticed that the "CSV/TXT: Read" action ignores the last column in a CSV if that column is null, despite the column having a header?
For example, if you open the following CSV and read it:
| key | val1 | val2 | val3 | val4 |
| 1001 | “StringData” | “StringData” | ||
| 1002 | “StringData” |
| “StringData” |
|
Your data table will only have 4 columns, “key”, “val1”, “val2”, and “val3”; “val4” will be omitted.
This seems like an oversight to me and I think it should be fixed in future releases. I think we should at least have the option to toggle “headers” on and off to tell the “read” action how to interpret our files.
EDIT:
The “read” action appears to read the final column, but you can’t reference it. For example, I have a CSV with 14 columns, and the last is blank. When read into a DataTable, the table column count is 14, but when I reference index “13” (which is the 14th index position), I get an error that the index is out of bounds. Very odd to me.