"Date Created" wrongly stays "1969"

[cmarkovsky]

I would really appreciate help if anyone has it! I am using the Open Source version of SugarCRM and when we are putting in our leads the "Date Created" field wrongly remains at 12-31-1969. Even if I manually punch in the correct date, once I hit "Save" it reverts back to the 1969 date. Can anyone help me with this problem? Thank you very much!

[kuske]

Very nice

Which locale settings do you have in Sugar ?

[cmarkovsky]

Thank you so much for replying! To be honest with you, I am not technically savvy at all - we're a start up company and as the marketing person, I ended up wearing the IT hat. So, I'm unclear as to what you mean by "locale settings" and where I can find those. So you know how we're using SugarCRM, check out our website (www.platinumvirtual.com) and see the two buckets on the right side ("Virtual Assistant" and "Business Owner"). On those two pages we have custom forms and when someone fills out those forms they go directly into our CRM as leads. What's interesting is that if someone were to fill out the form on our site, when it goes into the CRM it has the correct date. It's just when I (or any of my team members) wants to put in a lead manually via the CRM (not our website) that it comes up with the 12-31-1969 date. Any suggestions you may have would be super helpful - although I'll need to be guided through anything step by step! Thank you!

[kuske]

Ok, no problem, if you look to "MyAccount" you will see a section calles "Locale Settings", just as mine which I attached as a hardcopy here.

How does this look in your environment?

[Stratton]

I'm experiencing the exact same problem. Any ideas what could cause this? I just upgraded a new installation to the latest patch for 5.0 (5.0.0f). I also tried to manually correct it, but doesn't work. I think my locale settings are fine:

[stevec]

Hi,

I'm afraid it's not a solution - just an explanation. The date 1969-12-31 is probably a timezone/daylight saving converted version of the date 1970-01-01 in the sugar database. Datetimes are processed by sugar in Unix timestamp formats - and 1970-01-01 is the datetime representation of the value '0'.

Somewhere along the line, the system is having problems interpreting the value imported/entered and is defaulting it to nothing.

[DragonflyMaster]

Thank you so much for replying! To be honest with you, I am not technically savvy at all - we're a start up company and as the marketing person, I ended up wearing the IT hat. So, I'm unclear as to what you mean by "locale settings" and where I can find those. So you know how we're using SugarCRM, check out our website (www.platinumvirtual.com) and see the two buckets on the right side ("Virtual Assistant" and "Business Owner"). On those two pages we have custom forms and when someone fills out those forms they go directly into our CRM as leads. What's interesting is that if someone were to fill out the form on our site, when it goes into the CRM it has the correct date. It's just when I (or any of my team members) wants to put in a lead manually via the CRM (not our website) that it comes up with the 12-31-1969 date. Any suggestions you may have would be super helpful - although I'll need to be guided through anything step by step! Thank you!

The differences between insertion from form or manually on CRM makes me think that your Server's date is 12-31-1969...

[DragonflyMaster]

Ok,
I tried to import from a csv and mySQL give all records 01-01-1970 as creation date. So what I said in my previous post about your server's date is partly wrong and partly ok: it just means that in your mysql the earliest date is 12-31-1969.

[Stratton]

Well, I checked the server date, and it appears to be correct:
Fri Jul 11 13:21:59 EDT 2008

Do you think Sugar is the problem or MySQL?

[kbrill]

I would really appreciate help if anyone has it! I am using the Open Source version of SugarCRM and when we are putting in our leads the "Date Created" field wrongly remains at 12-31-1969. Even if I manually punch in the correct date, once I hit "Save" it reverts back to the 1969 date. Can anyone help me with this problem? Thank you very much!

If you have the date created field on your EditView then that's the problem. That field is special and cannot (it can but it shouldn't) be added to the Editview as any day put in there will be treated differently from other dates, it's hard coded. What is happening is that the system is trying to convert the date to GMT and it cannot because the date is entered in whatever date/time format you have chosen and it is expecting it to be in the default system format (mysql format if you will). If you remove the date Created field from the EditView it should go back to working.