StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POExchange 2010 Web Services - creation of an all day event appointment
text
Body
copied!<p>I got in trouble with creation of an all day event appointment using Exchange 2010 Web Services (EWS) .</p> <p>According to existing requirements to create an All day event appointment object needs to have specified start and end time (i.e. 10/20/2011 12:00:00 AM), and also timezone.</p> <p>But my application converted to use EWS instead of WebDAV sets start and end time converted to GMT (Greenwich) time which then sent to Exchange server. </p> <p>Such technique worked perfectly with WebDAV. But with EWS I get weird result: appointment spans on 3 (three) days, and is NOT All day event appointment !!!</p> <p>My mailbox timezone set to Pacific Standard Time (using OWA interface), and Exchange server Date and Time also set to Pacific Standard time.</p> <p>Appointment start and end times are set to “2011-10-20T07:00:00.000Z” and “2011-10-21T07:00:00.000Z” respectively. In terms of local time these times are “10/20/2011 12:00:00 AM” and “10/21/2011 12:00:00 AM” respectively (considering Daylight Saving time).</p> <p>If IsAllDayEvent property of appointment object set to False – appointment created correctly – not as All day, starts at 10/20/2011 12AM and ends at 10/21/2011 12AM, and occupies only one day – October /20/2011 in Outlook Calendar.</p> <p>But If isAllDayEvent property of appointment object set to True (everything rest remains the same) – appointment starts at Oct/19/2011 9:00:00PM, ends at Oct/21/2011 9:00:00PM, and is NOT All day.</p> <p>It might be that I’m doing something wrong, but based on described above following question raised for me: </p> <ul> <li>does EWS support Greenwich Time for All day events?<br> If yes – what might be my mistakes?</li> </ul> <p>I appreciate any suggestion. Sincerely Andrew</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload