-
Notifications
You must be signed in to change notification settings - Fork 90
Issues: Inteligenz/X12Parser
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Segment 'NM1*QD*1*CLAY*MARTONN*C' in segment position 26 within transaction '681560001' cannot be identified within the supplied specification for transaction set 837 in any of the expected loops: 2000A[1],2000B[2],2010BB. To change this to a warning, pass throwExceptionOnSyntaxErrors = false to the X12Parser constructor. Parameter name: 837
#18
opened Aug 31, 2020 by
mamohanma
837P Specification Does Not Include PER Segment For Loop 2010CA
#10
opened Oct 2, 2018 by
JeffFerguson
EligibilityTransformationService throws exceptions during parsing of responses
#9
opened Jun 14, 2018 by
tmccurdy
Missing ExecuteNonQuery in IIdProvider.LongHiLowIdentityProvider.EnsureSchema
#8
opened Apr 17, 2018 by
rpalbert
X12Parser is giving error for L11 tag in document type 210 for version 5010
#3
opened Feb 6, 2018 by
kanuj23
ProTip!
Follow long discussions with comments:>50.