Can somebody please explain this behavior :

{
  "VALUE": "2024-04-04T14:10:39+00:00",
  "d2": "2024-04-04 16:10:39"
}

d2 =

dateTimeFormat(value, "yyyy-mm-dd HH:nn:ss")

Good morning! Two things for you: 1. You're trying to output time information also, so you will want to use DateTimeFormat(). 2. DateTimeFormat defaults* to using the system's timezone as the basis for the calculation. See the timezone argument here: https://helpx.adobe.com/coldfusion/cfml-reference/coldfusion-functions/functions-c-d/DateTimeFormat.html

I meant DateTimeFormat 🙂 typo.

I figured, but better to be thorough. 🙂

I figured it was related to my system's timezone, but I could not wrap my head around it. Thank you for the feedback.

As in before passing it into DateTimeFormat()?

yes

That does appear to handle your situation. It's interesting to note that it appears that CF handles it by calculating the timezone offset, adjusting the date, and then dropping the timezone information from the timestamp.

{ts '2024-04-04 14:10:39'}

Both interesting and annoying 😄.

@James Harris -- it didn't show the timezone because he didn't have it in his DateTimeFormat string.

In his original example, value has it with the +00:00. Dropping that from the string prior to the DateTimeFormat() also works as desired.

if he would have used the "full" or "iso" formats, it would have shown the timezone in his output

Good additional information. Thank you, quetwo.

Thank you both for the feedback / input!

Pretty much, if you explicitly set the timezone /anywhere/ in the lifecycle of the variable, you then need to explicitly set it /everywhere/. If you are always timezone agnostic, then it will always reference your local timezone. The only pitfall with that is if your database sets it explicitly somewhere (like the MySQL driver likes to do), then you might still need to deal with it.