Help understanding EdiSegment Path settings

[raisr]

Help understanding EdiSegment Path settings

[cleftheris]

According to EDIFact (as well as the other 2 standards X12 and Tradacoms) inside of an EDI Segment such as UNB there is this a fixed structure. For example in your case.

• tag: UNB
  • element 0: UNOC:3
    • component 0: UNOC
    • component 1: 3
  • element: 1: 109910000
    • component 0: 109910000
  • element 2: 999999999
    • component 0: 999999999
  • element 3: 240315:1342
    • component 0: 240315
    • component 1: 1342
  • element 4: 00384
    • component 0: 00384
  • element 5: <Empty>
    • component 0: <Empty>
  • element 6: AO05Q224ke0
    • component 0: AO05Q224ke0

A path is composed by these 3 PathFragments separated by / like so <SegmentName>/<ElementIndex>/<ComponentIndex>. The component index is synonymous to the <ValueIndex>

A part (fragment) can be either:

1. Explicitly declared (full path)
2. a wildcard * in order to enable CLR class reusability. In essence this enables a definition on an [EdiElement] class as a set of reusable component values under a different Segment context.
3. Missing a part. This case is either because it is implied zero (on a component/value property) or because it is marked on an Element or Segment class.

Check out an older question here #179

Although your example should be working on first glance there may be something else going on. Can you add a pull request with a failing test.

[raisr]

Thanks. That helped me.

[cleftheris]

I forgot to mention that in cases where elements repeat multiple times (with variable count) inside of a Segment there is a special notation on order to map them to a collection instead of mapping them to multiple properties of the same type like Element1, Element2, ElementN

Like in this case: https://github.com/indice-co/EDI.Net/blob/master/test/indice.Edi.Tests/Models/EdiFact_Issue190.cs