Dynamic Flat File Import uses wrong THUNK_COLUMN length.
Issue:
It appears that the column length is being picked up from whatever we set the THUNK_COLUMN length against the Flat File Connection manager rather than the destination table individual column length's.
Solution:
Set the THUNK_COLUMN column type to DT_WSTR and length to 250 in the Flat File Source component.
When column length is set to DT_WSTR and length 250 for the flat file source, the code will trigger to configure the source column type to match the destination column.
For database destinations, that process works. However, if the user connects flat file destination where there is no columns metadata, that algorithm doesn’t work well for the situations where the column length exceeds 250 characters. When the customer changes the source column length, the source columns length is no longer applied based on the destination. The changed column length in the flat file source will now be the default during the initialization.
Book a Presales Call
Related Articles
Error Message: The Flat File Source.Outputs[Flat File Source Output].Columns[THUNK_COLUMN] has an invalid error or truncation row disposition.
Action: When executing a package using Data Flow Task Plus within a Foreach Loop and a Flat File Source, the first iteration of the loop succeeds, followed by the following error message on the second iteration of the loop. Error Message: ''The Flat ...Dynamic Data Flow - How to create completely dynamic data flow?
Starting from 1.4 SR-3 the data flow can be completely dynamic - the need to have one common column across different iteration sets is no longer required. To have completely dynamic components, you have to remove all statically defined columns (both ...Dynamic Data Flow - "... is DT_NTEXT, which is not supported with ANSI files" when trying to process input Unicode flat file
Trying to process input Unicode flat file fails with weird error: The data type for "Flat File Source.Outputs[Flat File Source Error Output].Columns[Flat File Source Error Output Column]" is DT_NTEXT, which is not supported with ANSI files. Use ...Dynamic Flat File Import uses wrong THUNK_COLUMN length.
Issue: It appears that the column length is being picked up from whatever we set the THUNK_COLUMN length against the Flat File Connection manager rather than the destination table individual column length's. Solution: Set the THUNK_COLUMN column type ...Dynamic Flat File Import uses wrong THUNK_COLUMN length.
Issue: It appears that the column length is being picked up from whatever we set the THUNK_COLUMN length against the Flat File Connection manager rather than the destination table individual column length's. Solution: Set the THUNK_COLUMN column type ...