Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
5 replies
Subscribers
10 subscribers
Views
1717 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Data and Records
I have an issue in my record listview timestamp where the date shows up incorrec
jamalu
A Score Level 3
over 8 years ago
I have an issue in my record listview timestamp where the date shows up incorrectly. The timestamp is set to rf!startDate which is a CDT field of type Date. This variable shows up correctly in my database and in the summary view of that record(i.e. 3/07/2016) when passed from rf!startDate, but in the timestamp in the listview shows up as Sept.6 2016, which is 6 months and a day earlier. I also checked by using a a!queryEntity function to select the date and the date is correct there. Does anyone know why this is happening in the listview timestamp field?
OriginalPostID-199351
OriginalPostID-199351
Discussion posts and replies are publicly visible
0
Tessy
over 8 years ago
Hello
Are all of your time-zones (between the DB, and your Appian user) the same?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jamalu
A Score Level 3
over 8 years ago
Yes, all of the time zones are the same
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
siddharthg837
over 8 years ago
Hi Jamalu, in your timestamp field of list view , can you try wrapping the below expression around your date time field.
gmt(ri!date,usertimezone(ri!user))
where ri!date is your data time value returned by your query entity as you mentioned above and
ri!iuser will be the loggedInUser()
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jamalu
A Score Level 3
over 8 years ago
I tried the expression that you provided and the date still remains incorrect
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jamalu
A Score Level 3
over 8 years ago
I figured out the issue. I mistakenly concatenated a string to my date, and that was causing the constant offset.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel