Record Producer has a date/time reference field that is showing 5 hours more than the table has stored

[Bob]

Looking at the table, the entries are showing the correct date/time stamp, but when I pull this into a record producer, it is showing 5 hours into the future.

Straight from the table:

What the record producer shows:

Apparently this is something that was happening in Fuji, but nobody noticed it, because it didn't give any errors and still saved to the table the correct time.

Now we get this error:

[Patrick Schult2]

Dates are saved to the database as GMT so they can be correctly displayed in the user's local time zone in the UI. I find it suspicious that you are seeing a 5 hour difference in these times because Lexington is 5 hours offset from GMT.

Try looking at what the actual date stored in the database is - you can view this by viewing the current record as XML (context menu > Show XML). You would expect the time you see there to be 5 hours ahead, so if the correct local time is 02-21-2017 14:44:12, you would expect to see 02-21-2017 19:44:12 in the XML.

If that is not the case, then take a look at what sets that value into the database - if a script is saving it, ensure it's using a method that either accounts for time zone, OR sets it using GMT.

If the database does in fact have the correct time, see what happens when you make that field editable instead of read-only - maybe there's a bug with how read-only affects time conversion?

[Bob]

So yes, I am seeing in the XML the GMT value stored is the correctly 19:44:12.

Funny the field was only used for visual purposes so we just removed the field. I'll check the field when I have more time.