In 3.12, the string format "YYYY MM DD" was accepted by decimal-date-time and was returning the correct information
Now the same form in 3.13, returns this:
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.
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.
Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
