Values in Date Field Change in Table to Different Value After Edit is Made

[JessePinchotFDT]

I am having issues with data stored in a date field in a table used in Field Maps published via ArcGIS Online. I have manually edited the data to reflect the correct date for the records stored in the table (it should be 7/2/2025) and every time I go back to check on the data, it shows up as something else such as 7/3/2025 or 7/1/2025. Anyone else experiencing this issue and what is the resolution?

[CodyPatterson]

Hey @JessePinchotFDT 

Which field are you changing? Is it one of the archival fields like Editdate and Creationdate? If so, those may overwrite when edited or be different when created. If this is a custom date field then the data may not be saving properly. Does this happen when you create a new feature with a date, or does this happen only when editing preexisting features?

Cody

[JessePinchotFDT]

I'm changing a custom date field. I manually updated this data in the table many times to 7/2/2025, but as you can see it continues to show up as 7/1/2025

[DanGruber]

We've discovered that in some cases ESRI changes stored dates/times in local time zone to GMT. This happened to us when we downloaded an attribute table as an Excel. You might check whether the incorrect dates/times actually are what you entered converted to GMT.

[JessePinchotFDT]

I'm in Eastern time zone so maybe the manual edit I make to 7/2/2025 thinks it's GMT, but then the update sends it back to Eastern?