Date being converted to an invalid date automatically by system

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-18-2016 02:52 PM
Hello, We are having issues with the ServiceNow date formats in our dev instance.
The system automatically converts the date format to include the timezone string "EDIT" at the end and this prevents from being able to save records.
Example:
2016-10-18 16:23:12 --> Was changed by the system automatically --> 2016-10-18 00:00:00 EDT
Steps to reproduce:
Open an existing or new incident and assign it to Service Desk
Put in a date in the "Due Date field"
The system strips off the time, and adds the timezone "EDT" at the end of the date.
The date then fails validation with "Invalid Date".
This was strange since it started happening randomly today on our Dev instance. I was working on something unrelated and did not make any changes to the date configuration.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-21-2016 01:06 PM
There are two other reports in the community:
https://community.servicenow.com/thread/230330
https://community.servicenow.com/thread/235348
The solution for some has been to log out and back in again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-26-2017 02:10 PM
1. Go to sys_properties.
2. Open the properties with name "glide.sys.time_format"
3. Change the value to HH:mm:ss
4. Anything after ":ss" should be removed. (eg, HH:mm:ss a or HH:mm:ss z)