decimal-date-time change between 3.12 and 3.13

301
2
Jump to solution
09-21-2021 10:33 PM
OlivierDemars1
New Contributor III

In 3.12, the string format "YYYY MM DD" was accepted by decimal-date-time and was returning the correct information

OlivierDemars1_0-1632288705632.png

 

Now the same form in 3.13, returns this:

OlivierDemars1_1-1632288732368.png

 

0 Kudos
1 Solution

Accepted Solutions
JamesTedrick
Esri Esteemed Contributor

Hi @OlivierDemars1 ,

I can see issues with a space separated date. That being said, I don't believe Survey123 explicitly supported a space separated date for parsing dates; the ISO convention of hyphenated dates was what was expected to be supported.

View solution in original post

2 Replies
JamesTedrick
Esri Esteemed Contributor

Hi @OlivierDemars1 ,

I can see issues with a space separated date. That being said, I don't believe Survey123 explicitly supported a space separated date for parsing dates; the ISO convention of hyphenated dates was what was expected to be supported.

MathieuBoonen
Occasional Contributor

I see similar odd behaviour when a survey saved on Arcgisonline (survey123) under our organisatuion in New Zealand, the date changes to a value that looks to be  GMT instead of NZDT or NZST 

see screen scrape of  the data in survey123 online and the same record exported as csv or a excel document the correct date is that within the online app, but something is doing the conversion to GMT?? on the export  function.

Help Please.

0 Kudos