I have a survey which captures a datetime. When entering data via the browser, or even editing/viewing an existing survey entry via the browser (mode=edit&globalId=xxx, or even mode=view), I see a nicely formatted split date/time display. In this survey the datetime field is not read-only:

If I have another survey pointed to this same underlying dataset and in this survey the datetime field is marked as read-only (i.e. using a dashboard to edit a survey entry, with some fields r/o), I see this:

Which is a very unfriendly way for a casual user to view the datetime field.
Is there any way I can force a better format when in read-only mode for this field?
Thanks,
Tom S.
Hi Tom
This is a known issue with read-only dateTime fields in the web app. Please log a bug through Esri Support if you'd like to track any progress on this issue.
One workaround could be to show this information in the second survey in a note question. You could format the date and time using the format-date() function (see Formulas—ArcGIS Survey123 | Documentation for more info). For example:
format-date(${datetime},'%m/%d/%Y %H:%M')
You could then use the hide=field: URL parameter to hide the dateTime question. Hope this helps.
Cheers,
Jim
Thanks Jim - the note will work just fine.
Tom
Hi Tom,
This is fixed in the web app and will be available on the next 3.11 release planned for mid Oct. Would you mind have a try then?
Thanks,
Jody Zheng Liu
I needed to have a readonly date field appear in my form with the intent of hosting a web map as an element in an experience builder map that integrated survey123 into the map's popup. the form was developed using Survey123 connect, and when i would test it as desired (thru Experience Builder) the date field was still editable. I finally got the date field to be uneditable by configuring my date field in survey123 as described below:
1) create a date field type
2) set appearance to Hidden
3) set readonly to YES and default to "today()"
then created a new text field type - set it to required and read only and set the entry in the calculation column to format-date(${date_field_name},'%m/%d/%Y'). solved my issue.
hope this methodology works for others trying to do something similar with different field types!