Flat File conneciton manager for import, and another for error exporting
OLEDB destination for successful data.
Transforms connecting the flat file source to the OLEDB destination on success, and to a script component, and eventually a flat file destination in the event of an error.
Very basic - take rows from a flight file, pipe delimited (CR/LF for rows) source, and map it into a table, exporting records that would error out into an error file.
Given a 3 row file (just for test), where the first record is missing a column, we wind up with 2 records (the record that we know has the error, plus the following record) in the error file, and only the 3rd record in the success file. One one record is
reported as going to each file (so, the error transform shows a single record, even though two wind up in that file). The couple of lines of code that move things over are as follows...
_erroredRow = System.Text.Encoding.ASCII.GetString(Row.FlatFileSourceErrorOutputColumn.GetBlobData(0, (int)Row.FlatFileSourceErrorOutputColumn.Length));
Output0Buffer.Record = _erroredRow;
What I suspect is happening here is that the delimiter at the end of the first (error) record is being missed, and thus what appears as two rows (and they do each have the appropriate CR/LF) is being treated as one.
Any hints as to why this is happening a
View Complete Post