Can't Create object from class c506_2 that nested from class RFF_2 that nested from class RFFLoop1 that nested from class CNILoop1

[indice-co]

Can't Create object from class c506_2 that nested from class RFF_2 that nested from class RFFLoop1 that nested from class CNILoop1

[cleftheris]

Hi @hamed22222 on a first look it seems that you have nested EdiMessage inside an EdiSegment class. This is not permitted. If you need a structure like that you will have to use SegmentGroupAttribute on the outter class and the segment & element attributes inside. You can check for an example here. In order to help you out further I will need to see the code model that is failing along with the sample.edi file.

[gk7gk7]

EFACT_D95B_CUSCAR.txt

[gk7gk7]

@hamed22222 can you send us a sample EDI payload?

[hamed22222]

Sample EDI.txt

[hamed22222]

that's my problem class called (c506_2) doesn't generate instance

[cleftheris]

We will create a new test for this using the SegmentGroupAttribute and get back to you

[hamed22222]

Waiting for your Response ,thank u

[gk7gk7]

We made some of the mapping involved using your sample and your model. You can find it here:
EdiFact_D95B_CUSCAR.cs
I have also created a test case with the assertions. Off-course this is a huge transmission & we did not cover everything but you will get the point.

Just for the sake of completeness there are some rules to have in mind when mapping EDI transmissions to CLR classes:

Classes that are decorated with Segment, SegmentGroup, Message, Group or Interchange consume the segment that defines the contrainer and cannot be reused inside them. If that makes sense you cannot have a Segment loop class RffLoop and an otherone inside Rff mapped to the same segment. The inner one will not map. The solution is simple: just map the properties of the segment to the container class (RffLoop in the example above).

Regards

ps: As documentation for the D95B transmission we used this resource https://www.stylusstudio.com/edifact/D95B/CUSCAR.htm.