
Hi all.
We're in a bit of a desperate straight here. We just released some code into the wild over the weekend that broke our ASN process. We discovered that the XSD Schema had been modified as part of the new code release and the field mappings were no longer in the correct order. We modified the base query (AxdASN) to reflect the order of the fields as they should appear in the XSD Schema, but when we go to Tools->Update document service and select the option to Regenerate data object classes, the XSD file does not reflect the changes we made. We also rolled back the solution that was causing the issue, but it appears that simply rolling it back will not resolve the issue because the XSD file is incorrect.
Does anyone have any advice on how to resolve this? Because the field definitions are out of order, every attempt to send an ASN fails and my EDI administrator is starting to lose his mind.
Thanks for any advice you may have.
Brandt
*This post is locked for comments
I have the same question (0)Hello
If you linked the document class with an outgoing port, first unlink the class from the port.
Then, after having created or updated the document services, please go to the apropriate service in AOT, right click and choose "Add-Ins" / "register service". In the new window, you can refresh the services.
Now you should be able to link the document class with new schema to the outgoing port.
Then please perform a ful CIL and restart the AOS.
If you run the service with a batch job, you have to delete the old batch job before and recreate a new one, because the execution class is cached in the batch job.
Tell us, if this helps
Regards
Hans-Peter