Table - trigger after update being ignored

Hi Mel

Swap

if FirstName = " " and LastName = " " and GDPR = 3 then

for

if FirstName = null and LastName = null and GDPR = 3 then

Regards John

I'm having a similar issue.

My 'Trigger on create' is non fuctional. Was working up till approximatly the 13th of July and then just completely stopped. I have tested it with a simple text field being filled out and that still doesn't work. 

Seems there is a larger issues at play with the recent update.

and to clarify, I'm using the web version as well. The simple test script that I have been using is below.

'Fill me in' := "Hello"

I contacted Ninox and someone is taking a closer look at the issue for me. I'll post the finidings.

On a side note, I have found that the issue is constrained to only the one table in the database, and constrained to only the web verson.

The issue isn't present if you use the one of the Ninox apps (ie iPad or Mac).

FYI this is still an issue, it works fine on the Iphone App. but not the web version.

Hi David, 

thanks for bringing this up again, as I had forgotten to post about my finding. The people at Ninox had a look at the database and were able to recreate the issue to a varying degree depending on which device they were using. They weren't however able to pinpoint the problem. They just said that it was strange, and suggested some workarounds. 

After about another month of fiddling and implementing workarounds with buttons, I stumbled upon the cause. It had to do with the date field and the trigger after update code attached to this field.

The date field was set to "Today" as the default value, and the trigger after update code made reference to a linked table (1:N). The issues was the when the record was created, there were not any linked records attached, and since the trigger after update on the date field must run when it automatically puts in today's date, it must kill all the other triggers when it cannot complete its trigger.  

My best guess as to why this was only an issues on the web app and not the iPad/iPhone apps must have to do with the order the the trigger events occur. The web app must process the trigger after update before it runs the trigger on create, and iPad/iPhone apps must run the other way around. 

Hope this helps and make sense.