AlexMedina.Edi
1.12.0
dotnet add package AlexMedina.Edi --version 1.12.0
NuGet\Install-Package AlexMedina.Edi -Version 1.12.0
<PackageReference Include="AlexMedina.Edi" Version="1.12.0" />
paket add AlexMedina.Edi --version 1.12.0
#r "nuget: AlexMedina.Edi, 1.12.0"
// Install AlexMedina.Edi as a Cake Addin #addin nuget:?package=AlexMedina.Edi&version=1.12.0 // Install AlexMedina.Edi as a Cake Tool #tool nuget:?package=AlexMedina.Edi&version=1.12.0
AlexMedina.Edi
EDI Serializer/Deserializer. Used to read & write EDI streams.
This is a ground up implementation and does not make use of XML Serialization
in any step of the process. This reduces the overhead of converting into multiple formats allong the way of getting the desired Clr object. This makes the process quite fast.
Tested with Tradacoms, EDIFact and ANSI ASC X12 (X12) formats.
Using attributes you can express all EDI rules like Mandatory/Conditional Segments, Elements & Components
as well as describe component values size length and precision with the picture syntax (e.g 9(3)
, 9(10)V9(2)
and X(3)
).
Quick links
Installation
To install Edi.Net, run the following command in the Package Manager Console. Or download it here
PM> Install-Package "AlexMedina.Edi"
Attributes.
The general rules of thumb are :
Attribute | Description |
---|---|
EdiValue | Any value inside a segment. (ie the component value 500 in bold) |
UCI+001342651817+9907137000005:500+9912022000002:500+7 | |
EdiElement | Elements are considered to be groups of values otherwise known as groups of components. One can use this attribute to deserialize into a complex class that resides inside a segment. For example this can usually be used to deserialize more than one value between + into a ComplexType (ie the whole element into a new class 9912022000002:500 in bold) |
UCI+001342651817+9907137000005:500+9912022000002:500+7 | |
EdiPath | To specify the path |
EdiSegment | Marks a propery/class to be deserialized for a given segment. Used in conjunction with EdiPath |
EdiSegmentGroup | Marks a propery/class as a logical container of segments. This allows a user to decorate a class whith information regarding the starting and ending segments that define a virtual group other than the standard ones (Functional Group etc). Can be applied on Lists the same way that [Message] or [Segment] attributes work |
EdiMessage | Marks a propery/class to be deserialized for any message found. |
EdiGroup | Marks a propery/class to be deserialized for any group found. |
EdiCondition | In case multiple MessageTypes or Segment types with the same name. Used to discriminate the classes based on a component value |
Example usage:
There are available configurations (EdiGrammar
) for EDIFact
, Tradacoms
and X12
. Working examples for all supported EDI formats can be found in the source code under tests.
- EdiFact sample POCO classes
- TRADACOMS sample classes (UtilityBill)
- X12 sample classes (850 Purchase Order)
Note that all examples may be partialy implemented transmissions for demonstration purposes although they are a good starting point. If someone has complete poco classes for any transmition please feel free to contribute a complete test.
Deserialization (EDI to POCOs)
The following example makes use of the Tradacoms
grammar and deserializes the sample.edi
file to the Interchange
class.
var grammar = EdiGrammar.NewTradacoms();
var interchange = default(Interchange);
using (var stream = new StreamReader(@"c:\temp\sample.edi")) {
interchange = new EdiSerializer().Deserialize<Interchange>(stream, grammar);
}
Serialization (POCOs to EDI)
In this case we are instantiating our POCO class Interchange
and then fill-it up with values before finally serializing to out.edi
.
var grammar = EdiGrammar.NewTradacoms();
var interchange = new Interchange();
// fill properies
interchange.TransmissionDate = DateTime.Now;
...
// serialize to file.
using (var textWriter = new StreamWriter(File.Open(@"c:\temp\out.edi", FileMode.Create))) {
using (var ediWriter = new EdiTextWriter(textWriter, grammar)) {
new EdiSerializer().Serialize(ediWriter, interchange);
}
}
Model
Annotated POCOS example using part of Tradacoms UtilityBill format:
public class Interchange
{
[EdiValue("X(14)", Path = "STX/1/0")]
public string SenderCode { get; set; }
[EdiValue("X(35)", Path = "STX/1/1")]
public string SenderName { get; set; }
[EdiValue("9(6)", Path = "STX/3/0", Format = "yyMMdd", Description = "TRDT - Date")]
[EdiValue("9(6)", Path = "STX/3/1", Format = "HHmmss", Description = "TRDT - Time")]
public DateTime TransmissionStamp { get; set; }
public InterchangeHeader Header { get; set; }
public InterchangeTrailer Trailer { get; set; }
public List<UtilityBill> Invoices { get; set; }
}
[EdiMessage, EdiCondition("UTLHDR", Path = "MHD/1")]
public class InterchangeHeader
{
[EdiValue("9(4)"), EdiPath("TYP")]
public string TransactionCode { get; set; }
[EdiValue("9(1)", Path = "MHD/1/1")]
public int Version { get; set; }
}
[EdiMessage, EdiCondition("UTLTLR", Path = "MHD/1")]
public class InterchangeTrailer
{
[EdiValue("9(1)", Path = "MHD/1/1")]
public int Version { get; set; }
}
[EdiMessage, EdiCondition("UTLBIL", Path = "MHD/1")]
public class UtilityBill
{
[EdiValue("9(1)", Path = "MHD/1/1")]
public int Version { get; set; }
[EdiValue("X(17)", Path = "BCD/2/0", Description = "INVN - Date")]
public string InvoiceNumber { get; set; }
public MetetAdminNumber Meter { get; set; }
public ContractData SupplyContract { get; set; }
[EdiValue("X(3)", Path = "BCD/5/0", Description = "BTCD - Date")]
public BillTypeCode BillTypeCode { get; set; }
[EdiValue("9(6)", Path = "BCD/1/0", Format = "yyMMdd", Description = "TXDT - Date")]
public DateTime IssueDate { get; set; }
[EdiValue("9(6)", Path = "BCD/7/0", Format = "yyMMdd", Description = "SUMO - Date")]
public DateTime StartDate { get; set; }
[EdiValue("9(6)", Path = "BCD/7/1", Format = "yyMMdd", Description = "SUMO - Date")]
public DateTime EndDate { get; set; }
public UtilityBillTrailer Totals { get; set; }
public UtilityBillValueAddedTax Vat { get; set; }
public List<UtilityBillCharge> Charges { get; set; }
public override string ToString() {
return string.Format("{0} TD:{1:d} F:{2:d} T:{3:d} Type:{4}", InvoiceNumber, IssueDate, StartDate, EndDate, BillTypeCode);
}
}
[EdiSegment, EdiPath("CCD")]
public class UtilityBillCharge
{
[EdiValue("9(10)", Path = "CCD/0")]
public int SequenceNumber { get; set; }
[EdiValue("X(3)", Path = "CCD/1")]
public ChargeIndicator? ChargeIndicator { get; set; }
[EdiValue("9(13)", Path = "CCD/1/1")]
public int? ArticleNumber { get; set; }
[EdiValue("X(3)", Path = "CCD/1/2")]
public string SupplierCode { get; set; }
[EdiValue("9(10)V9(3)", Path = "CCD/10/0", Description = "CONS")]
public decimal? UnitsConsumedBilling { get; set; }
}
Build the sourcecode
As of v1.0.7 the solution was adapted to support the dotnet core project system. Then it was adapted again since the dotnet core tooling was officialy relased (March 7th 2017 at the launch of Visual studio 2017). In order to build and test the source code you will need either one of the following.
- Visual studio 2017 + the dotnet core workload (for
v1.1.3
onwards) - Visual studio 2015 Update 3 & .NET Core 1.0.0 - VS 2015 Tooling (for versions
v1.0.7
-v1.1.2
) - VS Code + .NET Core SDK
for more information check .Net Core official page.
The Picture clause
The Picture Clause is taken from COBOL laguage and the way it handles expressing numeric and alphanumric data types. It is used throughout tradacoms.
Symbol | Description | Example Picture | Component | c# result |
---|---|---|---|---|
9 | Numeric | 9(3) |
013 |
int v = 13; |
A | Alphabetic | not used | - | - |
X | Alphanumeric | X(20) |
This is alphanumeric |
string v = "This is alphanumeric"; |
V | Implicit Decimal | 9(3)V9(2) |
01342 |
decimal v = 13.42M; |
S | Sign | not used | - | - |
P | Assumed Decimal | not used | - | - |
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 is compatible. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 is compatible. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. |
-
net6.0
- No dependencies.
-
net7.0
- No dependencies.
-
net8.0
- No dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.
Version | Downloads | Last updated |
---|---|---|
1.12.0 | 112 | 5/6/2024 |
- Support deserializing message fragment without interchange #137
- deserialize Functional group headers and trailers into a separate class #138
- Revisited Element List deserialization and serialization #121
- Fixed paths with wildcard fragments (segment and element) now serialize fine.
- Fixed writer serializing boolean values #141.
- Fixed EdiSerializer bug when using Serialize overload that passes a plain `TextWriter` the internal EdiTextWriter was never closed thus not autocompleteing/terminating the current active structure #142.
- Fixed EdiReader when empty segment was found without segment name delimiter #152.
- Introduced new `SuppressBadEscapeSequenceErrors` option on the serializer. it is used to suppress the exception error thrown when a malformed escape sequence is encountered #157.
- Rolledback v1.9.10 `EscapeCharacters` change #160.
- Introduced new `EscapeDecimalMarkInText`. It is used by the EdiTextWriter to escape the decimal mark character inside text values #160.
- Added new path fragment notation for ranges. This allows for element ranges inside of a segment to be mapped to one structure while others to be mapped to #170.
- Bug fix related to nested segment group structures with the same segment name #172.
- Bug fix for Wildcard paths working only for collections #170.
- Fix for segment collection serialization. When some collection items where being serialized as elements instead #168.
- Fix missing path (non existing) on condition attirute should not enter infinite loop #188
- Fix whith the EdiFragment IComparer implementation. When there is an index vs a range. #190
- Fix Failing to deserialize when segments and segment group begin with the same segment and use condition. #196
- Control counts now autogenerated on Serialization :) Use EdiCountAttribute. #17, #113, #161