Hi Steven, Thank you for your quick response. Unfortunately, all the error events are empty. So, I tried your method with the dispatch element. At first it didn’t work either, then I added a delay to the dispatch and… it works! As I said, when the submission is done, I update my instance with the server’s response (@xml:id and @localType value, etc.) and then I perform the next submission, maybe all these actions are asynchronous or performed simultaneously, and it produces a conflict? The @delay would allow to really execute the next submission at the end of the entire process?
Best, Josselin. > Le 4 févr. 2021 à 22:25, Steven Pemberton <[email protected]> a écrit : > > <message>Submission error. > error-type: <output value="event('error-type')"/> > error-message: <output value="event('error-message')"/> > response-status-code: <output > value="event('response-status-code')"/> > response-reason-phrase: <output > value="event('response-reason-phrase')"/> > resource-uri: <output value="event('resource-uri')"/> > </message>
_______________________________________________ Xsltforms-support mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xsltforms-support
