Hi all, here’s a solution for the time computation, which potentially could serve as the basis for cross platform push notification solution for Glide:
Several services, such as ClickSend, permit scheduled SMS delivery through an https:// API (in addition to more full featured RESTful JSON payloads). To use most of these requires conversion of human readable time/date data into Unix time, which is computed approximately as the seconds elapsed from midnight on the date Jan 1, 1970 (latter known somewhat erroneously as Unix Epoch–Unix actually went live in 1972). I say ‘approximately’, because Unix time skips leap seconds; for applications not requiring atomic clock accuracy, you should be fine.
Using a simple array formula, it’s easy to set up a column with that 1970 date. You can then perform a simple date-time subtraction, and multiply this by 86,400, which converts days into seconds (required for Unix time). The Glide date-time calculation carries forward the fractional days elegantly, so the user does not have to separately add back in hours and minutes–that’s a very nice freebie.
However, it’s important to remember that Unix time is based on UTC, formally GMT (Greenwich Mean Time in the UK). So for example, if one is operating in the Eastern US, one has to add in the 5 hour (EST-UTC) timezone difference; in seconds, that’s 18,000.
So, Unix time = ((Glide_event_start_time - Unix_Epoch_date)*86400) + 18000 [EST only]
That works just fine, and I’ve checked this against Unix Time stamp servers. It’s nice that Glide handles all the fractional day (min, sec) portions elegantly.
Hope this helps. My aim is that using an OpenLink action to call an SMS service one can schedule a message at the appropriately scheduled time. Voila, push notification.
Hope this helps…