Duration field with different time zones
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-29-2016 08:35 AM
I've created a duration field and set the value to 4 hours
If I log in with a user in another timezone and open the same record and check the field it'll display another duration (in this case a user 1 hour ahead of me based on their location).
I've no idea why this is happening and it only happens a few times, most of the time the correct value is shown.
Anyone else who has seen this and can explain why it's happening? It's quiet a big difference in 1h downtime and 0h downtime.
This is what it looks like in the history for the record. Only by opening the record the downtime was changed.
I've had the exact same scenario in another instance as well and struggle to understand why it happends.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-30-2016 03:07 AM
Working as expected for me. I think you should call HI.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-30-2016 03:11 AM
Same for me, works 95% of the times, but sometimes it get this hickup.
Will try to gather as many cases as possible and send to HI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-30-2016 02:03 AM
Can you please share the field dictionary in advanced view?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-30-2016 02:19 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-30-2016 02:32 AM
In the audit history, if updated by is logged in user then try to debug mode and check if any script is acting on this field.