-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Double UNB segment after creating EDIFACT #235
Comments
Hi @GingerNinjaa can you add a pull request with a test that showcases the issue. This way I may be able to give it a try. |
I'm encountering the same - the string values in the object are getting output as a separate UNB before the nested objects in their own UNB I saw that there was a PR created for this at #236 - does that help diagnose the issue? |
Hello @cleftheris, Cna you tell me if this issue is solved? if yes what is the solution? |
As a workaround I went with post-processing the output and merging all the UNB lines together. It's gross but it gets the job done
|
Thank you @EionRobb this work for me |
Hi @GingerNinjaa thanks for the sample. I got this pinned down to property path substitution when using wildcard segments o the Segment definition itself. The wildcards where not substituted and when the UNB properties where ordered to prepare for serial write the element 4 what written before element 1. This made the serializer write a new element since it thought that the new path was starting from scratch. |
Double segment serialization when using wildcard paths #235
@EionRobb @GingerNinjaa The fix is up on nuget v1.12.0 |
Hi,
I dont understand why I have double UNB segment when I deserialize my poco to EDIFACT. Could you pelase help me find the issue?
XML file
Output File
POCO obiect part
The text was updated successfully, but these errors were encountered: