I have a Query Result column that returns dates in ISO format (2026-04-24T13:00:00). The problem is that Glide reads it as text, not as a date — so I can’t use date filters like “is before”, “is after”, or “is within” on it.
Things I’ve tried that didn’t work:
Format Date column → always outputs text, useless for filtering
Math column pointing to the Query Result → still shows as text in If->Then->Else, no date operators available
The only workaround I found was a JavaScript column that compares the date manually using new Date(p1), which works but gives me a text output, not a real date column.
My question: Is there a native way in Glide to convert a text column into a proper date that Glide recognizes as a date type — so I can use it in filters, conditions, and If->Then->Else with date operators?
I have a date in Fecha del servicio but when i use the Text to Date column it never gives the same time because of the time zone.
The problem is that i cant specify an specific timezone because we operate in 6 different cities with 4 different timezones, so if i specify a timezone it will show a wrong time in the other 5 cities
Im guessing a solution would be create and if else column to identify the city and depending of the city, apply an specific timezone, but is that the only turn around??
Or im not using the Text to Date column correctly?
The date in Fecha del Servicio comes from an API connector and doesn’t include a timezone. This is intentional — we store the raw local time of each city we operate in, so the time always reflects the local time wherever the service takes place.
For example: 2026-04-24T13:00:00 means April 24, 2026 at 1:00 PM local time, regardless of which city the service is in and regardless of which city my internal team is in, we all see the same time)
Since we operate across multiple cities in different timezones, storing the local time directly (without any timezone offset) is the simplest approach for us. Does that change how the Text to Date column should be configured?
Yeah that’s tricky, especially since you are giving it a moving target by not having a date and time in a consistent timezone. Text to Date is not something I’ve ever needed to use. I think the Text to Date column assumes you are giving it a local time and is trying to give you GMT time as a result based on your local timezone, unless you specify a timezone which adjusts it from that GMT time.
When you don’t have a Z at the end of your date and time, I think it’s applying the local offset twice. 5 hours to calculate to GMT and another 5 hours to calculate back??? Doesn’t quite make sense to me why it does that.
When I add a Z to the end, then I get something more predictable. I still get GMT, which is 5 hours ahead of my local time, which makes more sense.
I think I understand what you are trying to accomplish and I’ve spent a fair bit of time trying to figure it out myself. I feel like I’m missing something obvious, but I’ve come up with a hacky workaround. This honestly doesn’t make logical sense to me, but it seems to work.
