Trigger on Update not triggering

As I explained, the trigger code is written specifically to only run when appropriate and I have checked this with an alert() so I could be sure it was 100% correct. It runs ALWAYS when required and NEVER when not.

The button perfectly achieves what it is supposed to. It creates the desired child records - perfectly.

The problem is that if the alert() in the Trigger on Update code is simply replaced with the code that is in the button, nothing happens.

I used the the same process for Trigger on Create. Checked that it was triggering (not complicated, not additional criteria to check) and that the button code worked. Then copied the button code into the Trigger. That works. When a new parent is created, the appropriate child records are created.

This however fails with the Trigger on Update. The trigger runs when it should and the code does what it's supposed to, but only when run from a button and not from the Update trigger.  I even included the alert() along with the code copied from the button, so I could see if anything was actually running. However, no alert dialog.

So, when the trigger is only the alert(), it works when it should. If the trigger also contains code to create the child records, it is not run.

I cannot see how to perform a more exact test. Each part works perfectly, 100%. Put them together? Nah. Nothing.

I'll reply again with the code.

This is the code I used to test the Update Trigger:-

if (number(Cylinders) = 1 or (Cylinders and Configuration)) and Type and not 'Numeric spec dataⁿ' then
alert("get params")
end

That works, so when changing anything, if those criteria are met, the alert dialog is displayed.

The button code is:-

let thisEng := this;
let thePars := (select 'engineⓅs' where number(Id) < 10 and Parameter);
if lower(text(Type)) = "electric" then
thePars := thePars[lower(text(Parameter)) = "weight"]
else
if number(Cylinders) = 1 then
thePars := thePars[lower(text(Parameter)) != "angle"]
else
if number(Configuration) != 5 then
thePars := thePars[not (lower(text(Qualifier)) = "cylinder" and lower(text(Parameter)) = "angle")]
end
end
end;
for p in thePars do
let d := duplicate(p);
d.('Engine¹' := thisEng)
end

I previously tested the above just creating a text output to be sure it was basically correct, and then changed to the above which actually creates the child records. It works, correctly, every time, on the button.

Replace the alert() line in the trigger with the above button code and the code is not executed. 

The only thing that occurs to me is that the trigger checks for there being no child records and if that's the case, it creates some. Is Ninox being too clever and looking ahead, sees that there would be records if it was executed, which would then fail the original check and so doesn't execute the tigger? It does seem rather coincidental that the code to execute would change the trigger condition. Doesn't seem like the correct behaviour, but is that possibly what is causing Ninox to not trigger?

In my case, it appears to not be triggering at all. I tried including an alert(), but it was never displayed. Mind you, did I read something somewhere that Trigger on Update simply won't show an alert() even if included? Or did I dream that?

However, No child records were being created. First thing I did when troubleshooting was to check the child table and no records has been added. So they weren't being created but not linked.

In the end I decided the use of a button was better interface design, so this is no longer an issue, but it would be interesting to find out exactly what the bug is. Unless anyone can put forward a valid reason why this behaviour is correct?

Ignore my first comment about no alert() in Update Triggers. I was using that when first testing, so they definitely do display.

I think we need to pass this to support so they can try to fix it sometime.