date_entered always null (epoch) using API

**jlw253** · 2011-07-20, 04:20 AM

Version 6.1.3 (Build 5640)

I am using the Sugar web service interface via VisualStudio 2010 generated c# client.

I am using this client to create new Contact and Opportunity records using set_entry and a NV list with all the desired fields and their values.

For some mysterious reason, the "date_entered" field always ends up as 1970-01-01 (the epoch date) when I create new contacts and opportunities. I am populating the "date_modified" field in exactly the same manner and that field is being persisted properly.

I have searched this forum, Google and the Sugar bug list but can't find any indication that this problem is any bigger than something stupid in my code.

Has anyone run into the same issue? How did you resolve it?

**Angel** · 2011-07-20, 04:27 AM

This is usually a date formatting issue. Give this post a look from my blog: http://cheleguanaco.blogspot.com/201...and-dates.html

**jlw253** · 2011-07-20, 12:55 PM

Angel -

Thank you for your response. It got me thinking and re-evaluation my Local / UTC conversions.

It was as simple as having swapped the two -- I was putting the date_entered out in the future (rather than "in the past").

FYI for anyone with a similar issue -- Sugar's response was to simply discard the invalid date and use the epoch without complaining anywhere.