Hello,
I've been adding features into my survey recently to make filling it out more streamlined in the field. One such feature is to have time fields disregard daylight savings time adjustments made by the device the survey is being completed on with a Javascript calculation.
In the xlsx below, I have a hidden time field that gets the current time using now() when (${field_30}) is filled out. My visible time field then uses that timestamp as an input for the Javascript function which then outputs the time in Eastern Standard time.
This works well, however sometimes when the survey is submitted it replaces every single one of these calculated timestamps with the time the survey was submitted. (There are 10-12 of these timestamps that get calculated).
My guess is that the hidden time function S1R_TimeCalc is the culprit. the calculation "now()+int(${field_30})-int(${field_30})" but I could not think up a more elegant way to get a timestamp when another question is filled out.
Unfortunately, I cannot reproduce this issue. It has happened to multiple people though and seems to occur at the time of submission from the mobile app.
You should just be able to have your hidden "S1R_TimeCalc" field be relevant based on "field_30" being filled out. That way it is null until that question is filled, upon being relevant it is calculated while still be hidden from view.
Also all date/time fields are stored as UTC, it only displays based on your device setting. So unless you are trying to display the time in EST, You might not need to go through those extra steps.
Maybe I am missing something?