Hi Jolyon, thanks for replying me. The questionnaire is added by API call but the problem is that this call happens in a lot of different integrations and classes and in many different ways (due to a previously bad code management there is not a single primitive class being invoked but several), so they basically asked me to somehow resolve the problem at its root and set the default value through an UDF. I don't know why the OnBeforeSave isn't triggered by the API call and this surprised me honestly, maybe is an issue related to the particular TrakCare version or to the Region/Edition code but I'm not allowed to fix/modify it unfortunately.
However, so you're saying that with an OnBeforeSave is possible to set/modify the %request value? Doing for example something like:
set Q31 = %request.Get("Q31")
If ((Q31 = "") || (Q31 = 0)) {
Set %request("Q31",1)=1
}and the object will be saved with the overwritten value?
Hi Timo, thank you for your response and clarifications! As I wrote to Jolyon now is it clearer how %d and %old variables work in OnSQLTrigger UDFs.
I agree with Ali and do the same. Quit is to escape out of a code block, while return is at the end of the code to return a value. Moreover, I use a lot the Try-Catch statement and Quit is not valid inside the Try block to return values but only inside other statements to escape out of them.