Why the library is outputting SegmentCountNotMatching error even when SE has the proper value?
I have the following scenario. An 837p with the following structure for a CLAIM.
Following the standard the REF segment is out of place and the library properly detect that on the ACK generation process but when ACK generation finish if I call IsValid then the MessageContextError now contain SegmentCountNotMatching even when the SE has valid counter for segment.
Any approach or step i'm taking wrong?
Could you please raise support requests together with order id here ?
I have an EF Enterprise Plan with order ID, what is the way i should ask for supporting.
Could you please raise support requests by clicking on the link below:
Is this resolved? I am having the same issue, can you provide the solution?
If the message can't be parsed properly, e.g. some segments are displaces and therefore were not parsed, the resulting object will have its HasErrors set to true. This means that at least 1 segment wasn't parsed.
When the validation runs, the segment count matching will fail, because at least one segment would be missing (the REF in the example above.).
Technically, you don't have to run IsValid when HasErrors is true, because the message had already been flagged as invalid.
Please go here for more info on partial parsing.
The way to go around is to create a version of the template, where all segments follow the correct order as per the specification.
Please sign in to leave a comment.