laptop and a wrench

Bug

Updating the date field using the Attribute Inspector sample from ArcGIS API for Javascript 2.8 saves the incorrect dates.

Last Published: August 31, 2014 ArcGIS API for JavaScript
Bug ID Number NIM079740
SubmittedApril 6, 2012
Last ModifiedJune 5, 2024
Applies toArcGIS API for JavaScript
Version found10.0
Program languageJavaScript
Operating SystemWindows OS
Operating System Version7
StatusWill Not Be Addressed

Additional Information

There are no plans to address this issue for an unsupported version.

Workaround

Change the code to reflect the correct time zone. Since the feature is a UTC timestamp, the JavaScript code is converting to the users' timezone, which (assuming in the US) is four to seven hours earlier than midnight of 8/15/2007, which is why it is returning one day earlier.

As per the forum link:

<a href="http://forums.arcgis.com/threads/53385-SQLServer-datetime-field-doesn-t-translate-properly-as-javascript-date-object?highlight=date" target="_blank">http://forums.arcgis.com/threads/53385-SQLServer-datetime-field-doesn-t-translate-properly-as-javascript-date-object?highlight=date</a>

Below is the method which we need to use

function CustomDate(featureTime) {

console.log("formatting function called", featureTime);

// get the timezone offset from UTC time

var tzoffset = new Date().getTimezoneOffset();

// add the time zone offset to the timestamp

var utctime = dojo.date.add(new Date(featureTime), "minute", tzoffset);

return dojo.date.locale.format(utctime, { "selector": "date" });

}

Steps to Reproduce

Bug ID: NIM079740

Software:

  • ArcGIS API for JavaScript

Get notified when the status of a bug changes

Download the Esri Support App

Discover more on this topic

Get help from ArcGIS experts

Contact technical support

Download the Esri Support App

Go to download options