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 t
What error do you get?
Hint, use:
Submission error.
error-type:
error-message:
response-status-code:
response-reason-phrase:
resource-uri:
Hi Steven, hi all,
Unfortunately, when I use the last method
(submission/action[@ev:event="xforms-submit-done"]/send) I get an error with
the second submission. I don’t know why I have this error as everything seems
OK and it works with the "iteration method" or with the "@while method (if all
Hi Steven,
Thank you very much for your answer. I don't know why I didn’t think of it
before, as I use this method with another form… but not for a loop.
It’s simple and efficient!
Just for my personal understanding, do you know (or anyone else) how works
ev:defaultAction and if it’s fully i
One way would be to submit just one, and let the xforms-submit-done event
handler initiate the next.
save
Steven
On Wednesday 03 February 2021 15:33:21 (+01:00), Josselin Morvan wrote:
Hi all,
With one of my forms I have a « submissio
I was initially too lazy to check if a handler for submit-done was allowed to
initiate a submission using the same submission element, but then my shame got
the better of me and I looked it up. It is, so this is better (and I also added
the necessary if= that I forgot to add):