Closed olelis closed 2 weeks ago
Hi, it's strange! I did it in my side both with 0.7.0 and master and they're the same (and no errors).... Did you do any more customization? Can you please test with dev-master? Have you upgraded edifact-mapping package?
@sabas Yes, it works with dev-master! Should it be released under 1.1.1 ? And yes, it was latest released version of edifact-mapping (v0.5.0)
The only minor issue left is that in the end of groups, under sectionControl and messageTrailer,, there is no segment group:
It is not an issue for us, but I am not sure why it is empty.
Left: dev-master
Right: v0.7.0
And yes, there are no modifications (you can see original code in linked repositotory)
@olelis published a 1.1.1 tag The empty segment group is correct there after further analysis, since in the segment table they're at the same level of the header fields https://service.unece.org/trade/untdid/d96a/trmd/orders_s.htm
@sabas Thank you , 1.1.1 works correctly!
And thank you for the work you do and fast responses!
Hello,
In our system, we have noticed that after updating to version 1.x of this package, all our purchase order's have empty delivery address. It was working correctly for version 0.70.
I have found example edifact file that have exact same error: https://developer.kramp.com/edi-edifact-d96a-purchase-order
As you can see, it has three NAD+ lines:
Each meaning different party.
Here is the example code:
If you run same code between different versions Please compare editest.json files in both folders you will see some differences:
Here is working example that compares between two paths. https://github.com/olelis/phpedifacttest
I have also compared output of Interpreter and Analyzer and looks like Analyzer reads all addresses correctly.
How can this be fixed in our end, or is there an error in interpreter?