Survey123 Date Only shows incorrectly on Report

[RMill]

Hello, 

Recently I made a survey with survey123 connect. Within the survey is a date field that is set to default to today(). Originally when I published the survey I did not change any data types, however I noticed for post processing that the date field automatically tacked on the time, so default information was "%Y-%M-%D %I:%M:%S %p format. The time portion is unnecessary, so I changed the date field to esriFieldTypeDateOnly in the bind::esri:fieldType column. Since I have changed the data type, the date now shows up incorrectly when reports are generated using the Survey123 website, and by incorrect I mean they show up a day behind. The date is correct in the table, such as 1/22/2025, but then it will show up as 1/21/2025 on the report. I copied the survey and tried different data types, with the standard date data type and string working properly, just not the "date only" type. 

I would like to try and not change the data type, but then it seems like the fix for that is on esri's end? Any information would be great, thanks!

[RMill]

I was reading back over the information in the link that SarahSinghNZ attached. It says that unlike the other date types, with date only "the field is stored as a string field in the ArcGIS Online feature data store". I'm not fully sure if it would apply in this case... but could this be it?

[LMedeirosUI]

I think this particular bit of information refers specifically to how you add the field to your feature layer. And should be reflected in the data type when looking at the field's information.

If you happen to know why my field is exporting to excel with a leading backtick (aka the grave accent), I would appreciate knowing. Doesn't matter if it's a timestampOffset or DateOnly bind::esri:fieldType - still get the leading backtick when exporting to Excel. No backtick when exporting to CSV format. Going crazy.