Sys Created On Date is very wrong

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-17-2015 11:42 AM
Hello,
We noticed some very strange results in our Metrics reports. The "Create to Resolve Duration" metric results show several hundred Incidents that have a Duration in thousands of years.
I was able to determine that the cause is the Sys Created On date on those affected Incidents is very wrong. There are several hundred incidents that have a Start Date from thousands of years ago in the *first century*, such as year 0019 examples 0019-12-10 23:44:29 and 0023-04-10 23:50:56.
The metric is calculating the difference between Created On date and the Updated On date, so that's why those durations are very large.
gr.start = current.sys_created_on;
gr.end = current.sys_updated_on;
gr.duration = gs.dateDiff(gr.start.getDisplayValue(), gr.end.getDisplayValue());
Since the Sys Created On date is generated by the system in the back-end, what could have caused this issue?
The problem seems to have only affected a subset of incidents thus far but has skewed our manager's reporting capabilities.
To summarize, the Sys Created On date on several hundred Incidents is showing dates from thousands of years ago.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-17-2015 11:45 AM
Hi Kathryn,
You may find the below thread helpful.
https://community.servicenow.com/thread/190893
https://community.servicenow.com/thread/159206
If this doesn't help then I would suggest to raise a HI ticket and update the thread.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-17-2015 11:46 AM
I would certainly suggest opening a ticket with HI. They'd be able to get down to the root of this issue pretty quickly.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-17-2015 01:21 PM
check the date format for the user ... we have discovered that quite often dates get set wrong if the uer has an odd date format in their preferences.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-17-2015 01:23 PM
Which user, the caller on the incident? Do you think that might be the case even though the Created On date is set by the system in the back end? Thanks for the response!