Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Working on parsing an 846 document #10

Open
melaniefedok opened this issue Jun 1, 2016 · 1 comment
Open

Working on parsing an 846 document #10

melaniefedok opened this issue Jun 1, 2016 · 1 comment

Comments

@melaniefedok
Copy link

melaniefedok commented Jun 1, 2016

Hello,

I am working through parsing an 846 document. I have created the XML file to match the specification, which I will need added to the project later when I have my testing complete. However, the EDI that I am being sent has the field separator set to '~' and the segment separator set to '*'. Is there a way to set the values to be used for these separators?

@mjpete3
Copy link
Owner

mjpete3 commented Jun 1, 2016

Melanie,

At the moment the segment separator, field separator and the composite
separator are set in the base class. This class is a child class of
loop, segment and field classes. The way the code sits today there
isn't an easy way to set the separators from within your project.

Normally the field separator is '*', the segment separator is '~' and
the composite separator is ':'.

The easiest and quickest way to make the change you need is to fork the
x12 code and in the base.rb file under the initialize method, set the
three separator variables to what you need.

Marty

On Wed, 2016-06-01 at 08:10 -0700, Melanie Fedok wrote:

Hello,

I am working through parsing an 846 document. I have created the XML
file to match the specification, which I will need added to the
project later when I have my testing complete. However, the EDI that I
am being set has the field separator set to '~' and the segment
separator set to '*'. Is there a way to set the values to be used for
these separators?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants