In the date/time field of the incident record, when the DisplayValue is checked, there is a 16-hour
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2024 06:53 PM
I have a problem with a 16 hour gap in the date/time field when performing the following. If you have other instances or solutions, please share information.
・Create an incident record using Inboud Action.
After creating the record, when Opened_at and sys_created_on are compared, Opened_at is registered with the date and time 16 hours in the future.
・When the date/time field (Opened_at) is used in the body of a notification in an incident record, the displayed time is shifted by 16 hours.
・An event record is created from an incident record by a script action.
When a custom date/time field is obtained, a 16-hour gap (in the past) occurs when the DisplayValue is checked, causing an operational error.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-11-2024 09:56 PM
how are you setting the value to record via inbound and how are you printing the value in email?
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-14-2025 05:47 PM
This issue has been resolved.
A user-specific time zone setting was required.
*The issue caused the instance's time zone setting to not be reflected, but this has now been resolved.