search

indice-co / EDI.Net

EDI Serializer/Deserializer. Supports EDIFact, X12 and TRADACOMS formats
MIT License
450 stars 170 forks source link

EDI Mapping #175

Open command0r opened 3 years ago

command0r commented 3 years ago

We were looking at EDI.Net and it seems a good idea to translate the EDI messages using EDI DOM (i.e. the POCO classes). Could you suggest if we can do the mapping between the standards as easy? What would be the right way to go here? If we plan to use it for multiple clients who expect different variations of the output messages, what's the best way to develop that kind of 'extensions'?

cleftheris commented 3 years ago

Hi @command0r and thanks for your interest in EDI.Net.

Although I have never done this myself, if the transmissions are of the same format (ie EDIFact) & message type (ie IFCSUM) but slighly different version "D05B" then there might be some reuse on the POCOs using base classes and ovveride attributes when needed.

Generally speaking in order to transform an EDI interchange from one format to another usually there is a completely different spec. Although, using a different EdiGrammar will take care of the syntax (delimiters terminators etc.) the POCOS will be bound to one transmission through attributes. The only way I can think of would be to have two distinct models and make the transformation in code (Using automapper or something similar). It maybe possible to reuse some base classes and annotate but not much.

Regars

C.

command0r commented 3 years ago

Got it, thanks.