Timezone/Timestamp Offset, Wrong or Ignored?

API & Customization
1

I opened a support ticket, but it’s a pretty confusing situation so I thought I’d get everyone’s advice while I wait…

My app is set with timezone: Pacific Time (US), which is GMT-08:00. It’s daylight saving time so it will be -7hrs now.

However, when I use the API or export my table in Builder, all the timestamp fields that should be UTC in the resulting JSON is not.

For example:

"field_300": "08/08/2024 4:53pm",
"field_300.unix_timestamp": 1723135980000,
"field_300.iso_timestamp": "2024-08-08T16:53:00.000Z",

This field has Default set to “current time”. So I have to assume the app DOES recognize my timezone setting as it’s correct in local time. But the other two timestamp fields which both should be in UTC are still in local time just in 24hour format.

Super confused, am I missing some settings or the use of API somewhere? Or does Knack simply not have the concept of timezones despite the app setting?

2

Hi Ken,

Knack doesn’t save timezone information as far as i’m aware. It’s been a challenge for my team in the past. We ended up creating another field for the timezone of the user and needing to reference another field.

1 Like
3

Thanks for sharing, good to know it’s not my app or some kind of misconfiguration on my end. Huge bummer tho, pretty surprising considering this day and age and throwing around unix and iso but being incorrect. :frowning_face:

4

For people who might see this post, I got a response from Knack Support. (They’re quick!)

They acknowledged the issue, but not so much a bug, it’s just that Knack currently doesn’t have the concept of timezones, just a display format for now.

We’ll have to implement our own workarounds, but we can at least vote here: Date/Time and Timer Time Zone Localization | FEATURE | Knack
The status is Planned so let’s hope this comes soon.

2 Likes