Date headaches

Question

I've been having headaches with dates in Appian and I think it has to do with the way appian handles timezones. 
 Unless I'm mistaken, appian is supposed to record dates in GMT then then later read them in whatever local time zone is appropriate. What I'm finding is that it records in the local time zone, then later reads it as though it were GMT and adjusts to the local time zone, resulting in incorrect dates. 
 The more frustrating thing about this is how I access/display the date affects what gets shown. 
 For example if I use a date picker, appian records the date as 4 hours earlier. Thus 8/8/2025 will be recorded in the db as 8/7/2025 8:00 pm EDT 
 If I display the date in a text field, I'll get 8/7/2025 8:00 pm EDT, but if I put it through any kind of function such as text() to format what it looks like it'll come out as 8/8/2025. 
 What's worse is I imported a csv of a bunch of legacy data and the dates were all converted to date/time and had the 4 hours subtracted when recorded. 
 How can I keep this from happening?

Shubham Aware · Answer

You're using DateTime instead of Date type. DateTime gets timezone-converted (causing your 4-hour shift), but Date doesn't. Switch your CDT fields from DateTime to Date type and use a!dateField() instead of a!dateTimeField(). For existing data, display with text(gmt(ri!dateTimeValue), "MM/dd/yyyy") to bypass timezone conversion. For CSV imports, use todate() not todatetime().

Stefan Helzle · Answer

https://appian.rocks/2023/02/13/working-with-time-in-appian/

Mike Schmitt · Answer

The functions local() and gmt() are your friends. It's tricky to remember how and when you can/want/need to use each, but with practice you will get used to it.

Stefan Helzle · Answer

Here we go! I suggest to contact Appian to discuss this and how to manage it.

Mike Schmitt · Answer

You have to remember that some date/timestamps are stamped with a timezone and some are not. A lot of the confusion comes into play when dealing with an inherently non-timezone-stamped time value (like "today()") but then dealing with that in the context of a time rather than as a date, when it inherently gets timestamped - and, of course, Appian treats all timestamps behind-the-scenes as GMT/UST, other than how they're displayed to the end user - this is where things like GMT and LOCAL come into play. 
 Marco Tacca said: I want the time zone in the db to at least be accurate 
 The "time zone in the db" is always accurate , as it's always GMT/UST. What you must straighten out is what the end user sees and what gets saved/retrieved, and often, this goes hand-in-hand with the developer's understanding thereof.

Mike Schmitt · Answer

Marco Tacca said: I'm getting either EST or EDT on the DB 
 How is that happening? If you use any standard funcitonality to store a standard timestamp into the DB, the datetime value should be stored as UST, unless you first applied an incorrect conversion, or something else unusual has happened to it first. 
 Edit: I now see your followup comment to Stefan explaining that the DB is not in cloud and hardcoded to be EST-centric. In that case I'm not sure what to do other than to make sure all in-Appian settings are set such that it expects everything at all to be in EST.

Harsha Sharma · Answer

In your process model , that writes record to this table , can you check the time zone is GMT in the process properties-> time zone . Also confirm that the checkbox &lsquo;Override with initiators time zone&rsquo; is unchecked. If its checked then the data will be stored as per the process initiator&rsquo;s time zone setting instead of GMT so you should have it unchecked! Let me know how it goes.

Date headaches

Top Replies