NIM079740 for ArcGIS API for JavaScript

Numéro d’ID de bogue	NIM079740
Envoi	April 6, 2012
Dernière modification	June 5, 2024
S’applique à	ArcGIS API for JavaScript
Version trouvée	10.0
Langue du programme	JavaScript
Système d’exploitation	Windows OS
Version du système d’exploitation	7
Statut	Will Not Be Addressed

Informations supplémentaires

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

Solution de contournement

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" });

}