How should dates be formatted when passed to the Update method in Consituent API?

Options

Our vendor is passing

custom_date2=3/11/2010 10:09:33 AM

and the field is not being updated in our Convio records. Is it the time that might be screwing it up? Or is there some other format that is required for the date.

Adrian

Tagged:

Comments

  • Adrian,

    Dates must be in ISO 8601 (http://www.w3.org/TR/NOTE-datetime), so it should be 2010-03-11T10:09:33.

  • Noah Cooper:

    Adrian,

    Dates must be in ISO 8601 (http://www.w3.org/TR/NOTE-datetime), so it should be 2010-03-11T10:09:33.

    Thanks Noah... passing that on to the Port.

  • Adrian Cotter:

    Thanks Noah... passing that on to the Port.

    Our vendor asks:

    Can you please ask them if the trailing "Z" is acceptable in their

    implementation of this format?

    i.e. "2009-03-13T10:20:33Z" vs "2009-03-13T10:20:33"

  • Adrian Cotter:

    Our vendor asks:

    Can you please ask them if the trailing "Z" is acceptable in their

    implementation of this format?

    i.e. "2009-03-13T10:20:33Z" vs "2009-03-13T10:20:33"

    Yes, including the Z for time zone is acceptable.

  • Noah Cooper:

    Yes, including the Z for time zone is acceptable.

    Or the timezone offset, I assume as well...

    +01:00 or whatever it happens to be?

Categories