What we get pushed to Remedy is something like: <ReceivedTime>2007-06-04T10:13:00</ReceivedTime> (The application calling our Remedy Web Service is the same time zone so the tz offset is not needed) I'm assuming you are using the US date/time format and your field is defined as type Date/Time with a Display of Date and Time Fred
________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Caruso Sent: Monday, June 04, 2007 10:29 AM To: arslist@ARSLIST.ORG Subject: Re: WebService Date Format ** No luck .... still kicks back Invalid Date Format On 6/1/07, Jarl Grøneng <[EMAIL PROTECTED]> wrote: Try this format: YYYMMDD or YYYY-MM-DD If this is a date/time, try this: [YYYY]-[MM]-[DD]T[hh]:[mm]:[ss]±[hh]:[mm] -- Jarl On 6/1/07, Frank Caruso <[EMAIL PROTECTED]> wrote: > ** OK .... I've tried every possible format for a date that I can think of > but I keep getting the following error message: > > MessageType: 2 > Messsage Num: 8957 > MessageText: The date format is invalid > > I've tried regular date formats as well as EPOCH. No luck. > > Anybody know what format to place in a SOAP call to Remedy for a date > (date\time) field? > > > > -- > Frank Caruso > Specific Integration, Inc. > Senior Remedy Engineer, ITIL Foundation Certified > www.specificintegration.com > 703-376-1249 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
