I have done some searches, but I can’t seem to get my hands around whats going on. The WebQuerySave agent just isn’t running. Other QSA’s are running properly for other documents w/ in this database.
I have a lot of code in the QSA and I removed it and just put one simple “print” statement and its still not running.
My submit button on the form calls, a javascript routine:
if (bConfirm){
f0.XP_StatusTx.Value = "30 - Submitted";
f0.submit();
}
Does the form save if the WQS is turned off? Will it (the agent) run if you submit the document using
@command([filesave]);@command([fileclosewindow])
?
Ideally, you would want to do this Javascript in the onSubmit event and call it with a button. This is just to avoid someone perhaps using a URL in the browser to submit the form, which would prevent your code in the button from running.
Using the @command should trigger the onSubmit, then the WQS agent. In your onSubmit handler, you would do your checks and return false if any fail, and true if they all pass, which moves things along to the WQS agent.
Don’t just concentrate on the WebQuerySave agent – the 500 can occur before the agent is called, when the submitted data is married to the form. That can mean other errors (uninterpretable date, data type conversion errors, input translations, etc.) on the form could be the actual problem. In particular, since you are dond and end run around the _doClick() function and not filling the __Click field, Domino may be having trouble figuring out what’s going on.
(I’m not a big fan of the Domino-generated JavaScript and turn it off when I can, but I’ve learned that it’s better to learn to live with it when it’s there than to try to fight it.)
Stan-Thanks for the information. Looks like I have some data issue somewhere. Need to figure what field(s) is causing the issue and hopefully we will be good to go.
Thanks for pointing me into the right direction, at least a direction I wasn’t thinking.