3.1.4.3.1 Copying a Calendar Object When The Source Object Is an Exception

When the source object is an exception, the client uses the RopCreateMessage ROP ([MS-OXCROPS] section 2.2.6.2) to create a new Calendar object. The client follows the same requirements for the new object, as already specified for copying a Calendar object. Furthermore, all properties that are not set on the Exception Embedded Message object, as specified in section 2.2.10.2, but that are set on the Recurring Calendar object are to be copied onto the new object. In addition, the following actions MUST be taken by the client:

  • The value of the PidTagMessageClass property ([MS-OXCMSG] section 2.2.1.3) MUST be reset to "IPM.Appointment" on the new object.

  • In addition to those already specified in section 3.1.4.3, the following properties MUST NOT be copied onto the new object:

    • PidLidAppointmentRecur (section 2.2.1.44)

    • PidLidRecurrenceType (section 2.2.1.45)

    • PidLidRecurrencePattern (section 2.2.1.46)

    • PidLidTimeZoneStruct (section 2.2.1.39)

    • PidLidTimeZoneDescription (section 2.2.1.40)

    • PidLidFExceptionalAttendees (section 2.2.2.3)

  • The value of the PidLidClipStart property (section 2.2.1.14) MUST be set to the value of the PidLidAppointmentStartWhole property (section 2.2.1.5).

  • The value of the PidLidClipEnd (section 2.2.1.15) property MUST be set to the value of the PidLidAppointmentEndWhole (section 2.2.1.6) property.

  • The value of the PidTagIconIndex property (section 2.2.1.49) SHOULD be set to 0x00000400 if the Exception Attachment object was attached to an Appointment object or to 0x00000402 if the Exception Attachment object was attached to a Meeting object.

  • The value of the PidLidRecurring property (section 2.2.1.12) MUST be set to FALSE.

  • When copying the RecipientRow structures ([MS-OXCDATA] section 2.8.3), the client copies them from the Exception Embedded Message object and not from the Recurring Calendar object.

Show: