Video Screencast Help

1753-01-01 00:00:00.000

Created: 24 Oct 2012 • Updated: 25 Oct 2012 | 6 comments
This issue has been solved. See solution.

Dear All,

I was asked to make a report that shows how many Break-Fix tickets have been handled by who in what month.

In the table "ServiceDeskIncidentManagement" the field "date_created" often shows this value: 1753-01-01 00:00:00.000 while the "Start Date" in the ticket is correct.

In what table can I find the "Start Date" field? Why is the "date_created" field often filled out with this value?

Thank you for your help.

Kind Regards

Koen

Comments 6 CommentsJump to latest comment

toomas's picture

Start Date should be process data, coming from ReportProcess table.

Why date_created would show that value, I am not quite sure. It's basically the NULL value for date, so the date_created was never properly filled for some reason.

SOLUTION
jpellet2's picture

I see that date_created field as 1753 a lot. We still haven't figured out why that field doesn't populate with the correct date. It will, from time to time, have the correct date but not often.

Jeanne's picture

I also get that 1753 in the date field on some dates but it is not consistent.

toomas's picture

Looking at the ServiceDesk 7.1 SP2 SD.IncidentManagement project, Incident.DateCreated is filled with current date in 'Save Process ID and Tracking ID to Incident Submitted By and Date Created' component in Primary model.

The problem with this is that when an Incident is created from Technician Feeder, it is sent to CreateIncidentAdvanced model that never goes to The Primary model (it goes directly to Main Incident Work).

Where are your incidents created from?

jpellet2's picture

That would do it. I would say that 90% of all of our tickets would go through the Advanced form so would bypass the components to update that field. I knew there was a reason I ignored it most of the time!