Strange Date conversion bug

Hi,

Can you try the following transform in your machine, I have included your data and added two new whole years 2022 and 2023, at my end none has any issues, can you try and see if you get the issue?

All tick mark are green which indicates no issue.

image

Transform file
FromClipboard2.transform (28.2 KB)

ok, new information,
There are 2 different offending dates. One for 2022, the other for 2023

03-09-2023 0:00:00
04-09-2022 0:00:00

I tried to ensamble all results in one screenshot:

Hi,

Well that mean, there is something wrong at your side, if you are using Windows OS then please check if your system need any updates, since Microsoft rolls out update quite often.

A part from that, since we can’t reproduce the issue you are having, we can’t do anything.

You did not say, how is that first file, which started all this, is working? did you do any change or it was like next time when you accessed it is working? or it worked after restart of the machine or what?

I can’t think of anything else, the file I setup for you, is working fine at my end as you have seen the screenshot.

Maybe some other users can download the transform and post their finding in here? to find out that it is just with you or others have the same issue?

Hi,

Looking at the dates that failed, it seems it has to do with month of September for you.

Copy the following dates and paste it into EDT, if my hunch is correct, then none of this should work for you, though it does work at my end.

Only September
01/09/2025 0:00:00
02/09/2024 0:00:00
03/09/2023 0:00:00
04/09/2022 0:00:00
05/09/2021 0:00:00
06/09/2020 0:00:00
07/09/2019 0:00:00
08/09/2018 0:00:00
09/09/2017 0:00:00
10/09/2016 0:00:00
11/09/2015 0:00:00
12/09/2014 0:00:00
13/09/2013 0:00:00
14/09/2012 0:00:00
15/09/2011 0:00:00
16/09/2010 0:00:00
17/09/2009 0:00:00
18/09/2008 0:00:00
19/09/2007 0:00:00
20/09/2006 0:00:00
21/09/2005 0:00:00
22/09/2004 0:00:00
23/09/2003 0:00:00
24/09/2002 0:00:00
25/09/2001 0:00:00
26/09/2000 0:00:00
27/09/1999 0:00:00
28/09/1998 0:00:00
29/09/1997 0:00:00
30/09/1996 0:00:00

Well, first of all… this is an amazing software
And you have all my gratefulness for the effort in support
I’m kind of used to be “the only user” with problems, as many software don’t work well with localization or other specific characteristics

some clarification:
a) I’m testing this in 2 PC’s

b) Only 1 Date, of September, each day, fails.
You can see the first images.

c) I just run 15.706 rows.
All dates from 1.jan.1990 to 31.Dec.2032

guess what… All the dates that fail are SUNDAYS…
AS Gordon said to Robin “you’re not allow to belive in coinsidences”

I repeat, only the first sunday of each September fails to convert

These are the only dates that failed, from 1.jan.1990 to 31.Dec.2032

Hi,

Well at least we found out what is the issue at your end and you know now.

Well, that is very strange. We call a function in the Qt library to do the conversion ( QLocale::toDateTime()). But I can’t reproduce the problem here, even if I set my locale to Spanish/Chile. Also no other reports of this issue.

Hi… just droping a line to tell that I found the problem (with the help of StackOverflow)

It was actually a Locale issue.

My PC is using Locale=Chile

In Chile clock is changed at 24:00 first Saturday of September, 0:00 of next Sunday doesn’t exist.

The workaround for me is to strip the “0:00:00” from the string before converting it to date.

To devs: You may not be using locale on your coding, but QT does use Locale for some functions, like date conversion.

Greetings, and closing this threat.

1 Like

Glad you found the cause. I didn’t seem to have this issue when I set my Locale to Spanish/Chile in Easy Data Transform Preferences window. So perhaps DateTime format uses the OS locale instead. I will look into that.

1 Like

I am still trying to work out why I am getting a different result to you when I set my locale to Spanish/Chile:

What is Locale set to in your Easy Data Transform Preferences window. Is it Spanish/Chile?

Dug into this a but more. It may be related to the time zone set in your operating system. You have your time zone set in Windows to Chile.

Ok, so I can reproduce the problem encountered by @SullyPanda76cl if I change my Windows time zone to Santiago. It disappears if I change it back to London. So mystery solved and it isn’t a bug. I will add a note to the Date Time Format documentation.