Re: When using tilde(~) as segment separator edi parsing breaks

This might not be related, but I have found in the past, when working on
Unix systems, that I had to escape the tilda character in order to use
it. Have you tried using the ascii code in your delimiters definition?

This might not be related, but I have found in the past, when working on
Unix systems, that I had to escape the tilda character in order to use
it. Have you tried using the ascii code in your delimiters definition?

Re: When using tilde(~) as segment separator edi parsing breaks

Hi Ashok,Check if your EDI file has a newline at the end of each segment. If that is the case, then you might have to change the delimiter definition in the mapping model file to include newline in addition to the tilde (~) character.

Or, for testing purposes, if newline is present, just remove it and test with your current mapping model.

This might not be related, but I have found in the past, when working on
Unix systems, that I had to escape the tilda character in order to use
it. Have you tried using the ascii code in your delimiters definition?

And also when I use only LF as segment breaker then also parsing
works fine. And also when I include any other character with ~ like
semicolon(;) then also parsing works fine but I am not getting why parsing
fails when there is a combination of ~ and LF at the end on each segment.

Hi Ashok,
Check if your EDI file has a newline at the end of each segment. If that is the
case, then you might have to change the delimiter definition in the mapping
model file to include newline in addition to the tilde (~) character.

Or, for testing purposes, if newline is present, just remove it and test with
your current mapping model.

This might not be related, but I have found in the past, when working on
Unix systems, that I had to escape the tilda character in order to use
it. Have you tried using the ascii code in your delimiters definition?

And also when I use only LF as segment breaker then also parsing
works fine. And also when I include any other character with ~ like
semicolon(;) then also parsing works fine but I am not getting why parsing
fails when there is a combination of ~ and LF at the end on each segment.

Hi Ashok,
Check if your EDI file has a newline at the end of each segment. If that is the
case, then you might have to change the delimiter definition in the mapping
model file to include newline in addition to the tilde (~) character.

Or, for testing purposes, if newline is present, just remove it and test with
your current mapping model.

This might not be related, but I have found in the past, when working on
Unix systems, that I had to escape the tilda character in order to use
it. Have you tried using the ascii code in your delimiters definition?

And also when I use only LF as segment breaker then also parsing
works fine. And also when I include any other character with ~ like
semicolon(;) then also parsing works fine but I am not getting why parsing
fails when there is a combination of ~ and LF at the end on each segment.

Hi Ashok,
Check if your EDI file has a newline at the end of each segment. If that is the
case, then you might have to change the delimiter definition in the mapping
model file to include newline in addition to the tilde (~) character.

Or, for testing purposes, if newline is present, just remove it and test with
your current mapping model.

This might not be related, but I have found in the past, when working on
Unix systems, that I had to escape the tilda character in order to use
it. Have you tried using the ascii code in your delimiters definition?

And also when I use only LF as segment breaker then also parsing
works fine. And also when I include any other character with ~ like
semicolon(;) then also parsing works fine but I am not getting why parsing
fails when there is a combination of ~ and LF at the end on each segment.

Hi Ashok,
Check if your EDI file has a newline at the end of each segment. If that is the
case, then you might have to change the delimiter definition in the mapping
model file to include newline in addition to the tilde (~) character.

Or, for testing purposes, if newline is present, just remove it and test with
your current mapping model.

This might not be related, but I have found in the past, when working on
Unix systems, that I had to escape the tilda character in order to use
it. Have you tried using the ascii code in your delimiters definition?

SV: When using tilde(~) as segment separator edi parsing breaks

Hi Ashok,

Sorry for the delay… was my last week before going on summer-holiday
and had tons to do at work. But now I have started my holiday and have had a
look at your files. I managed to read the edi-input you sent by adding LF
character to the segment delimiter.

And also when I use only LF as segment breaker then also parsing
works fine. And also when I include any other character with ~ like
semicolon(;) then also parsing works fine but I am not getting why parsing
fails when there is a combination of ~ and LF at the end on each segment.

Hi Ashok,
Check if your EDI file has a newline at the end of each segment. If that is the
case, then you might have to change the delimiter definition in the mapping
model file to include newline in addition to the tilde (~) character.

Or, for testing purposes, if newline is present, just remove it and test with
your current mapping model.

This might not be related, but I have found in the past, when working on
Unix systems, that I had to escape the tilda character in order to use
it. Have you tried using the ascii code in your delimiters definition?