topic Re: Date off by a month using Arcade in ArcGIS Pro Questions

Date off by a month using Arcade

Gisbert61 — Wed, 13 May 2020 09:37:26 GMT

A collegue used collector to record some records but a datefield wasn't filled. I decided to use arcade to fill the field:

But instead of May 11th I see June 10th. This is so confusing.

I understand that date is stored in utc but displayed in my local timezone (I'm near Amsterdam) so I was expecting some hours difference but this seems more than a month.

What am I doing wrong?

regards,

Bert

Re: Date off by a month using Arcade

KenBuja — Wed, 13 May 2020 15:47:45 GMT

When using the Date function, months are defined by 0-11 instead of 1-12.

month Number The month (0-11) where 0 is January and 11 is December.

Re: Date off by a month using Arcade

JonathanJew1 — Thu, 10 Feb 2022 17:55:23 GMT

Can anyone explain why the month() would be indexed at 0, while day() and year() actually returns what one would expect? Python treats months consistently, and I just can't wrap my head around why arcade would have been designed this way.

Re: Date off by a month using Arcade

DanThompson — Thu, 06 Apr 2023 20:21:57 GMT

yeah it makes no sense..

Re: Date off by a month using Arcade

bogrevy — Wed, 07 Jun 2023 08:16:25 GMT

Although it is stated in the documentation for both the Date function and the Month function, it makes no sense at all that this is 0-based.

The problem with changing that is that any existing arcade expressions that use these functions will fail. I would still recommend Esri to change these features instead of continuing to bear the pain all the following years.

Re: Date off by a month using Arcade

jfisher — Mon, 08 Jul 2024 16:32:53 GMT

This seems pretty insane to me: months are randomly zero indexed? Who would have checked off on this? This is clearly a bug.