Bad format special component current date/time

Hi, I’ve found a bug in date/time format component.
In special with Special component current date/time, that is very useful to automatically update modifications date/time.
My locale is set to Spain…dd/mm/yyyy, and the format in the google sheet date columns too.
When I update some field, I put the modified date/time value in a basic text component (to avoid be edit in non-edit mode)…

(date is october, 6, 2019)
this is the google sheet and you could see Glide change the presentation format in gsheets (non in the data)…
Here the glide apps with the modified data in format mm/dd/yyyy (oct, 06, 2019)

I think this behavior is common in all date/time component…

jesús ortega

I still believe if Glide switched to storing dates in ISO format(YYYYMMDD), that would solve a lot of problems for people. It’s an international standard recognized by Google and Glide and compatible across all countries. This still allows people to reformat the date into a new column if the user wants it in MMDDYYYY or DDMMYYYY.

I also need df/mm/yyyy and suffer from the problem in Israel

1 Like

I had requested this option in a previous post some time ago

1 Like

No, it’s not possible. That’s why I put this message.
As I have shown in the example (in the images) when Glide writes, it writes in the English format (mm/dd/yyyyy). Of course if you manually reformat the column is shown properly, but if you edit it again Glide records it badly…the problem is serious. (And of course de google sheet locale is Spanish (or dd/mm/yyyyy)…)
Do you plan to solve this?

@jrox10 Sorry if you misunderstood, I wasn’t offering a suggestion for you to solve your problem. I was offering a suggestion for Glide to store the dates in YYYYMMDD. I think this would solve everybody’s problem.

We could do ISO date/time format, which would be like 2017-03-13T15:00:00.000Z.

@Mark I think Google has issues with recognizing true ISO as a date, but with the limited testing I’ve done, I think replacing the T and Z with spaces would work. Basically the same format you already use, but moving the year to the front.

I think we have to differentiate between the way in which the date is saved and the way in which it is represented. A good model is like Google sheet (I attach an image…).

The problem now is that for days between 01 and 12, it is not clear what is being represented…for example if glideapps saves 11-10-2019, my users understand October 11, 2019, but Glide understands it as November 10, 2019…
Another option is to add a text field that allows you to format the date as you want with some mask or similar.

The Date and Date/time components do it correctly (I think) but the problem is that they are editable even in non-edition mode (…I don’t know why) and therefore I can’t users since the user could change an automatic date as the modification date (special component).

@jrox10 If Glide stored the date as YYYYMMDD, Google would recognize what is year, what is month, and what is day regardless of with country you are in. The calendar component also recognizes this format correctly. This would help solve the issue with days 1 through 12. It would also allow for easy sorting date.

For your issue of users changing the date, if the page is not supposed to be editable, use a text component to display the date instead of a date picker component.

@Mark my only concern with switching the date format would be if people are using a substring method to parse the date into a new column vs Text(). I wonder if it would be better to allow people to select a global date format for the app so they can choose if and when they want to change the format.

Edit: Disregard. Looks like you are already working towards that.

Glide writes dates as date/times into Google Sheets, so we’d just have to use a different format there: