
Recent Articles
Recent Blog PostsI have just posted a companion piece to the article I wrote last week on how to process rejected records. Last week I dealt with the more complicated case of processing records rejected by the Read...
jsiwila 05-14-2012 03:42 PM[LEFT][SIZE=3][FONT=arial]On the phone or on the road, I have been positioning expressor solutions that solve many data and application integration challenges. On a...
mtarallo 05-07-2012 02:15 PMfa·mil·iar...
mtarallo 05-02-2012 08:58 AM
Recent Forum PostsYes...That is correct. once I set that value as well, all is good. Thank you so much for sticking with me while we figured it out.
rjohnson Yesterday, 11:36 AM
When attempting to substitute a different database name to your dataflow you will need to substitute the "[Operator] Load Data Source@Write Data
tbayusik Yesterday, 11:34 AM
I thought the highest EXP_TRACE_LEVEL was 7, but I set it to 8 on the prod box. I tend to leave it on 4 there and set my dev box to 7 all the time for
rjohnson Yesterday, 10:56 AM
It would be helpful if you could create a windows environment variable called EXP_TRACE_LEVEL and set it to 8 and the re-run. Please send us the etask
tbayusik Yesterday, 10:46 AM
So I tried another data flow and I get the same error. When working without the substitution file, the data flow reads from the source and writes to
rjohnson Yesterday, 10:16 AM

Processing Records Rejected by a Read File Operator
Parsing records rejected by the Read File operator is simpler than parsing records from Read Excel and related operators. The Read File operator retains the sequence of fields and attributes when it writes them to the RecordData field of the Reject Record Schema. Because of that, it is not necessary for the Read File operator to write header records to describe the field and attribute sequence. That greatly simplifies the datascript required to parse the RecordData field and reconstruct the rejected records.
As explained in the Processing Rejected Records article, when a Read operator... read more