Starting 10/17, my Transactions sheet Categorized Date column (written by AutoCat) looks like this:
2024-10-20T02:36:08-0500
Which is text and Format as Date doesn’t change anything, because it is not recognized as a Date.
Previously, the cell content looked this and is recognized as a Date:
10/16/2024 2:36:13
Anyone else seeing this?
Hi @Mark.S - Yes I see that behavior in my sheet also starting also from 10/17.
I have received confirmation that it’s a bug. I don’t have an ETA for the fix.
And here is a formula that could be used in another column to create the corrected value that could then copy-paste values over the bad one:
=DATEVALUE(MID(Z2, 1, 10)) + TIMEVALUE(MID(Z2, 12, 8))
Where Z2 is the Transactions sheet Categorized Date column.
I see it also, starting 10/17. Is there any harm in leaving it that way? It doesn’t seem to have caused any problems for me.
AFAIK, there isn’t something that depends on it being a real date, but it’s easy enough for me to correct them to the intended date data. I’ll probably wait to correct them myself until after I see the fix go live, and then just do them all at once in batch.
We have pushed a fix for this issue as of yesterday Jan 2nd. It won’t fix any entries that were already using the incorrect format but new entries going forward will include Date & Time, which can be formatted to just Date if you prefer. I believe the timezone being used is PST, just a heads up on that.
I confirmed it’s PT, so this is still a bug, just traded one problem for another.
Date Added is spreadsheet timezone, Categorized Date should be too.
Now I have Categorized Date with dates occurring before Date Added (midnight Date Added with the day before Categorized Date) - it’s bad data.
Before this original bug was introduced, it was correctly spreadsheet timezone - why not revert back to that?
Ugh, sorry about that, I’ll see if that’s an easy fix. At least you can reformat it now 
@Mark.S we pushed another change to fix the timezone issue. Let me know if it’s better for you now too!
I confirmed it’s all good now, @heather 
Thank you so much for the quick fix to the update! 
