dateTime calculation now() returning WEIRD date in web app via Experience Builder

326
2
12-20-2023 04:28 PM
Teresa_Blader
Occasional Contributor III

readonly, dateTime field, now() in calculate field returns REALLY random date in Survey123 Web App. 

Time is correct. Date very odd. Works as expected in Connect.

This is an editing survey to fill out some fields that weren't available in form 1. 

Read Only no = dateTime field is blank, offers "Recalculate" button - which produces correct dateTime.
Read Only yes= returns odd date

Tried adding a relevant question to dateTime for a previous select_one... same situation. 

What da heckin' am I missing?? Where is it getting 7/12/20 from?? My machine time is correct, and form 1 was submitted like 5 minutes beforehand. 🤔😬

Connect version (readonly =yes):Teresa_Blader_0-1703118129953.png

Web app version (readonly = yes)

Teresa_Blader_1-1703118168300.png

 

Teresa Blader
Olmsted County GIS Specialist
0 Kudos
2 Replies
abureaux
MVP Regular Contributor

Sounds like a browser issue. What browser? Is it up to date? Have you tried a different browser? Have you tried a “neutral” web page to see if it displays the correct time (E.g. https://www.timeanddate.com)? You said it works correctly in connect - have you tried the field app yet (they are slightly different sometimes, so would be nice to rule anything out there)?

0 Kudos
Teresa_Blader
Occasional Contributor III

Looks like I was seeing this in the Survey123 form via an Experience Builder dynamic URL window. Doesn't matter which browser (Chrome vs Edge... which are up to date).

My systems time is accurate.

 

Now: If I open the form as a new survey just in Chrome or Edge outside of ExB, it populates the correct date. HOWEVER, if I edit the existing record in Survey123 (Data > Edit) it populates this weird date from July. So this is NOT explicit to ExB. 

Today's date of choice is 07/12/26 

Teresa Blader
Olmsted County GIS Specialist
0 Kudos