I am working on a simple timecard app for my field technicians. The two schedulers in the office enter time in and time out, and the technicians approve these times in the app. I am having some difficulty with entering/calculating times. My schedulers absolutely hate having to use the time picker --they insist on being able to manually type the times.
So, I am having them enter the times as a text entry. This would work just fine; however, Glide automatically assumes that the date is the day that the entry was made. This causes problems because the schedulers will often enter the time in one day and time out the next. For example, they might enter the time in as 7:30 am today, and then tomorrow enter the time out as 3:30 pm. This should calculate to 8.00 hours, but since there are hidden dates, it calculates as 32.00 hours.
I have another column that calculates the date for each day based on the last day of the pay week, so I was thinking maybe I could somehow force the app to default to that date?
Is there any way for me to fix this issue without forcing my users to use the date picker or forcing them to type in the date for each entry in addition to the time? Thanks!!
I have a suggestion in mind, but first a question: do they need to enter the exact times, or would it be good enough to round to the nearest 10 or 15 minutes?
Okay, in that case what I would probably do is force the selection of a date, but instead of using a date picker use a choice component and default it to the current date. Then combine that with the entered times to calculate the actual date/time value.
Actually, just thinking about this a bit more - and assuming that a shift would never span two days - what you could do is simply ignore the date in the time out column. How are you currently calculating the duration?
I’m calculating the the duration using a date difference column.
Unfortunately, there are rare occasions where the shift spans two days. I could create a special case for these if needed so that the rest of it works.