EDI.Net
EDI.Net copied to clipboard
Upgrade to .NET6 changes the edi output
Hello, I have a project that produces EDI message for a few year, running well. (Core2.1) Now we have upgraded our project to (.NET6) Both projects use indice-co version 1.9.18.
But the output is quite different ... in our previous project using version Core2.1 the program produces the following edi output :
UNB+UNOC:3+TRADER.NL100009999.00+NTA.NL+211028:1433+21102814330905++++0++0 UNH+21102814330905+CUSDEC:D:96B:UN:NL015B
while in our new version .NET6 we have as output
UNA:+.? UNB+UNOC:3+TRADER.NL100009999.00+NTA.NL+211027:1254+21102712540856++++0++0 UNH+21102712540856+CUSDEC:D:96B:UN:NL015B UNH+
As you can notice , the program adds suddenly some extra segments ... UNA + segment and twice a UNH record instead of 1 ....
Do you have any idea where to look for Thank y so much !
addon, we see more and more differences
old situation , we have 1 segment VTD+J++IVR+PRD:MCE+:::BVN
new situation, the program seems to split the data over multiple segments ... VTD+J++IVR+PRD VTD++++MCE+:::BVN
@ronnyvdweyer have not tested in dotnet6. But I will check it out. Thanks for reporting.
Hi @ronnyvdweyer I have tested with the latest vs 2022 RC3 and the rc for the dotnet6 but all ~100 tests pass. Seems to me that something else must have changed after the upgrade on your source code. Just to be sure can you please provide with a pull request and a failing test.
Kind regards,
C.
Any update on this? Also did you by any chance enable the AutoEndSegmentGroups
setting? If so, please try again disabling it.
C.
Hi, Thanks! Sorry for late answer. I asked around about the progress and learned that
We found out that the upgrade in the old solution 1.9.12 towards 1.9.18 never took place.
So the behaviors described above can be attributed to the upgrade from version 1.9.12 towards 1.9.18. When we scaled down again to 1.9.12 it works well. So we can exclude the NET6.
Pretty soon I will do some test and try to upgrade again , step by step and see where it goes wrong i will pay attention to the AutoEndSegmentGroups setting.
Once again tank you very much ! R.