Stopwatch Issue

[Mike_Jones1]

Hi I’m having a few issue with the Stopwatch function.

Basically I have a form where people record downtime. I’m using the stopwatch at the top, so as soon as they enter a new entry they start the clock, put in the rest of their details and when it is complete they submit the form. Allowing me to record the time in minutes that had passed.

As it stand it records the start time perfectly, but it isn’t recording the duration as per it shows?

Is there maybe another way around this? Such as record the time the entry form is submitted?

Many thanks for any suggestions in advance.

[Jeff_Hager]

Read through this entire thread to better understand how the stopwatch values work.

View the duration of the stopwatch in USC

The start time is recorded when you start the stopwatch. This is so the script knows the elapsed time between the current time and when you started the stopwatch. When you pause the stopwatch, then it writes that elapsed value (in number of days) into the duration…so when you start the stopwatch again, it records the new start time and calculates the elapsed time from the new start time to the current time, but also adds the previous duration. They are really used to help the stopwatch script…

[Mike_Jones1]

Hi Jeff,

Thank you for the response. I get what the duration function is used for now.

Is there any way I can save the time a form is submitted instead? So I can use a math field to calculate the different in the start time and then the form submit time?

[Jeff_Hager]

You can add a date/time special value component to the form.

Special Values

[Mike_Jones1]

Hi Jeff,

Thank you again for the fast reply.

On testing the special values, it seems to record the time you open the form, rather than the time you finish and actually click submit.

Otherwise is there just a time field I can use in the form, rather than the default date time field?

Many thanks,

Mike.

[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…

[Mike_Jones1]

I did think was rather weird option, as potentially people could have the form open for an extended period of time.

The time would we be measuring would be minutes rather than seconds, I can appreciate how this would be a problem.

I’ll keep having a play around, thank you for the suggestions. Hopefully it is something Glide can look at in the future.

Many thanks again.