Stopwatch Issue

[Jeff_Hager]

Really? I’ll have to play with that. I’ve always been under the impression that the date/time special value always used the time that the form was submitted, but admittedly, I’ve never verified that. Keep in mind that a lot of glide computations happen every five seconds, so if you are testing the special value within a time of less than 5 seconds from opening the form, it’s possible that the value may not have updated yet (that’s just a theory…don’t hold me to that). You could try instead to add a date/time entry component and have the user enter their final date/time, but that’s not a great solution. You may want to look into creating a custom form, which would possibly give you a more accurate final time. With the Set Column or Add Row actions, you also have access to the date/time special value.

How do I create a custom form?

I’m just dropping this here so I have something to refer people to when they ask. This is a simple concept app (copyable), that demonstrates the following techniques: Building custom forms for adding and editing list items (as an alternative to the native forms provided by Glide) Preventing duplicate new entries using User Specific Columns and Relations Enforcing mandatory input items The use of visibility conditions and user specific booleans to control user flow There is nothing particula…