Query Task AMF Date Issue

[RobertScheitlin__GISP]

I have just noticed that queries using AMF set to true are returning date fields in UTC seconds and not an actual date object or date string in the API is this a bug?

[DasaPaddock]

This is by design in AGS Server 10. The behavior should be the same if you set useAMF to false which causes it to request a JSON response.

[RobertScheitlin__GISP]

Dasa,

   Ok, so why is it not decoded by the API as it is when you query using the service page and have the format equal to html?

[DasaPaddock]

To post-process the response would add additional overhead looking for all the date fields and new'ing Date objects. Typically an app developer will want to format the date presented to the user, so at that time, they can also first new a Date with the value.

[RobertScheitlin__GISP]

Dasa,

   Ok, so maybe you can help me with my issue then when I query a parcel that has a Sales_Date field of type esriFieldTypeDate it has a value of 11/25/1998 and when it is returned in JSON it is 911952000000. so when I use new Date(value) I get 11/24/1998 instead??? What gives, didn't you just say that developers can simply use new date?

[DasaPaddock]

The problem can be with the time zone. Trying printing date.toUTCString() vs. date.toString(). You can also check the value of the dateUTC property.

[RobertScheitlin__GISP]

Thanks Dasa,

   toUTCString worked for me.