Constantinos Leftheris

Hi @FRConceicao and thanks for your interest in [EDI.Net](https://github.com/indice-co/EDI.Net). Also thanks for sharing your work. - I have not come across a transmission with multiple interchanges yet but nothing seems...

Hi @command0r and thanks for your interest in [EDI.Net](https://github.com/indice-co/EDI.Net). Although I have never done this myself, if the transmissions are of the same format (ie EDIFact) & message type (ie...

Hi @ArturNadolski and thank you for your interest in [EDI.Net](https://github.com/indice-co/EDI.Net). DESADV is an EDIFact transmission so I dont see any reason why you would not be able to deserialize it...

Hi @Janakanty and thanks for your interest in [EDI.Net](https://github.com/indice-co/EDI.Net). To answer your original question the Start property maps to the constructor parameter startSegment (You don't need to use it explicitly)....

Hi @chz160 and thanks for the kind words. Yes this is true. This is related to #19 and it is not implemented completely to take into account the advise characters...

Hi and thank you for your interest in EDI.Net To answer your question, we do offer consulting services. Please send us an email at company[at]indice.gr describing your request.

Hi @NickMcG, you could make use of an additional structural class for elements and make use of the attribute `[EdiElement]`. Elements contain subelements (components) that are the values so in...

Hi @Pao-lino, although there are no ready classes for the exact transmissions above there are may common segments involved between EDIFact transmissions and there are models you can copy to...

@raholland79 A temp **workaround** until this is fixed would be to alter the default grammar with different presets: ``` csharp public class CustomX12Grammar : EdiGrammar { public CustomX12Grammar : base()...

sorry about that. My intention was to show how you could work around this by testing different character sets for the delimiters. Since it is not clear without the complete...