Survey123 date field constraints

[E_-_MarieCook__GISS_]

We have a Survey123 form in production for reporting wildfires and other incidents responded to by NJ Forest Fire Service firefighters. To avoid entry of future dates, a constraint was set for various date fields. See the formula being used in the image below, which is identical for all date fields being constrained.

Since implementing the form with the constraint, users have sometimes been unable to submit the form when today’s date is chosen. The issue seems to be occurring randomly. Within the form, some fields will be rejected with today’s date while others are accepted, despite the constraint formula being identical for all fields. Some users experience a successful submittal, but only after saving the survey to Drafts first, and submitting from Drafts immediately.

Users are utilizing Samsung Tab S4s and Dell laptops for data collection. To troubleshoot, I confirmed most recent versions of the Survey123 form and Android/Desktop apps are being used. We would like to keep this constraint but will have to remove it if the issue cannot be resolved, as it is delaying the reporting of emergency responses.

Thanks in advance for your help!

[JamesTedrick]

Hi,

Apologies for the delay in response.  The today() function stores a value representative of local 12:00 noon for the date in question (refer to the function table in Formulas—Survey123 for ArcGIS | Documentation ).  If you are trying to compare a whole date, I would suggest using format-date() to extract the day, month and year components and compare with the day, month and year of the date you are comparing.

[E_-_MarieCook__GISS_]

No worries, James! Thank you. That makes sense. We will give that a try.

[DataOfficer]

We have users experiencing the same issues. @E_-_MarieCook__GISS_  did James' suggestion resolve your issue?