A left-field one today.  I have not seen a way to change the record terminator in TI when dealing with flat files but hoping there is a way.

I have an issue where some of my data contains a Linefeed, Char 10 (Hex 0A).
Probably from an upload someone did from Excel where Alt+Enter was used to split the value across multiple rows for readability.

TI seems to pick up any of Hex 0A, 0D or 0D0A as a valid row terminator thus splitting the record into two and creating havoc.

Yes, this needs to be sorted in master data, at source but curious to know if there is a way to trap for this in TI or specify that 0D alone is the record terminator.
Short-term solution may be to use SED or Python to strip 0A's

Anyone have any ideas on how to change the row terminator?

A left-field one today.  I have not seen a way to change the record terminator in TI when dealing with flat files but hoping there is a way.

I have an issue where some of my data contains a Linefeed, Char 10 (Hex 0A).
Probably from an upload someone did from Excel where Alt+Enter was used to split the value across multiple rows for readability.

TI seems to pick up any of Hex 0A, 0D or 0D0A as a valid row terminator thus splitting the record into two and creating havoc.

Yes, this needs to be sorted in master data, at source but curious to know if there is a way to trap for this in TI or specify that 0D alone is the record terminator.
Short-term solution may be to use SED or Python to strip 0A's

Anyone have any ideas on how to change the row terminator?

A left-field one today.  I have not seen a way to change the record terminator in TI when dealing with flat files but hoping there is a way.

I have an issue where some of my data contains a Linefeed, Char 10 (Hex 0A).
Probably from an upload someone did from Excel where Alt+Enter was used to split the value across multiple rows for readability.

TI seems to pick up any of Hex 0A, 0D or 0D0A as a valid row terminator thus splitting the record into two and creating havoc.

Yes, this needs to be sorted in master data, at source but curious to know if there is a way to trap for this in TI or specify that 0D alone is the record terminator.
Short-term solution may be to use SED or Python to strip 0A's

Anyone have any ideas on how to change the row terminator?

A left-field one today.  I have not seen a way to change the record terminator in TI when dealing with flat files but hoping there is a way.

I have an issue where some of my data contains a Linefeed, Char 10 (Hex 0A).
Probably from an upload someone did from Excel where Alt+Enter was used to split the value across multiple rows for readability.

TI seems to pick up any of Hex 0A, 0D or 0D0A as a valid row terminator thus splitting the record into two and creating havoc.

Yes, this needs to be sorted in master data, at source but curious to know if there is a way to trap for this in TI or specify that 0D alone is the record terminator.
Short-term solution may be to use SED or Python to strip 0A's

Anyone have any ideas on how to change the row terminator?

A left-field one today.  I have not seen a way to change the record terminator in TI when dealing with flat files but hoping there is a way.

I have an issue where some of my data contains a Linefeed, Char 10 (Hex 0A).
Probably from an upload someone did from Excel where Alt+Enter was used to split the value across multiple rows for readability.

TI seems to pick up any of Hex 0A, 0D or 0D0A as a valid row terminator thus splitting the record into two and creating havoc.

Yes, this needs to be sorted in master data, at source but curious to know if there is a way to trap for this in TI or specify that 0D alone is the record terminator.
Short-term solution may be to use SED or Python to strip 0A's

Anyone have any ideas on how to change the row terminator?

A left-field one today.  I have not seen a way to change the record terminator in TI when dealing with flat files but hoping there is a way.

I have an issue where some of my data contains a Linefeed, Char 10 (Hex 0A).
Probably from an upload someone did from Excel where Alt+Enter was used to split the value across multiple rows for readability.

TI seems to pick up any of Hex 0A, 0D or 0D0A as a valid row terminator thus splitting the record into two and creating havoc.

Yes, this needs to be sorted in master data, at source but curious to know if there is a way to trap for this in TI or specify that 0D alone is the record terminator.
Short-term solution may be to use SED or Python to strip 0A's

Anyone have any ideas on how to change the row terminator?