4.3 Merged Free/Busy String

  • Article

The following example shows how the MergedFreeBusy string is created by the server for a specified set of free/busy status view options. The following is an example of the FreeBusyViewOptions element of a GetUserAvailability operation request.

 <FreeBusyViewOptions xmlns="http://schemas.microsoft.com/exchange/services/2006/types">
   <TimeWindow> 
     <StartTime>2008-01-30T00:00:00</StartTime> 
     <EndTime>2008-01-31T00:00:00</EndTime> 
   </TimeWindow> 
   <MergedFreeBusyIntervalInMinutes>60</MergedFreeBusyIntervalInMinutes> 
   <RequestedView>FreeBusy</RequestedView>
 </FreeBusyViewOptions>

The following is the CalendarEventArray element that is returned in the response.

 <CalendarEventArray xmlns="http://schemas.microsoft.com/exchange/services/2006/types"> 
   <CalendarEvent> 
     <StartTime>2008-01-30T12:00:00</StartTime> 
     <EndTime>2008-01-30T14:00:00</EndTime> 
     <BusyType>OOF</BusyType> 
   </CalendarEvent> 
   <CalendarEvent> 
     <StartTime>2008-01-30T13:30:00</StartTime> 
     <EndTime>2008-01-30T14:30:00</EndTime> 
     <BusyType>Busy</BusyType> 
   </CalendarEvent></CalendarEventArray>

The corresponding merged free/busy status string will be the following: 000000000000332000000000

Between 1:30 and 2:00 P.M., the mailbox has two overlapping appointments, one marked OOF and the other marked Busy. The merged free/busy status string for that slot has to be marked OOF. The no data value (4) is not returned in the merged free/busy status string.

For a description of how the merged free/busy status string is constructed by the server, see section 3.1.4.1.4.1.