Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.
Originally posted by: ejonesI've seen this before. The problem is that the header says to expect only two fields but then each record looks like it has three.
What I did to get around the error is use the FieldNames parameter on the Optional tab to give this last field a name. In the case you described, the value I'd put in FieldNames would be:
Test,Max,Dummy
Then this causes the header row to be read in like data so I used a Split node to filter out the header record. You could use something like this in a filter to get rid of that header row:
where execCount <> 1
And at the same time, that filter could also:
exclude Dummy