Attempting to add appointment attendee results in error "Cannot use personal contacts as recipients or attendees"

[officedev]

Attempting to add appointment attendee results in error "Cannot use personal contacts as recipients or attendees"

[jkaleta]

I also encountered this problem. In my case the scenario was that I was updating an existing contact, with a modified list of attendees.
In my tests it occurred with Exchange 2010, but not with 2013 (on Office 365).

The offending attendee looked like this:

<t:SetItemField>
<t:FieldURI FieldURI="calendar:RequiredAttendees" />
<t:CalendarItem>
  <t:RequiredAttendees>
    <t:Attendee>
      <t:Mailbox>
        <t:Name>Test ([email protected])</t:Name>
        <t:EmailAddress>[email protected]</t:EmailAddress>
        <t:RoutingType>SMTP</t:RoutingType>
        <t:MailboxType>Contact</t:MailboxType>
        <t:ItemId Id="AAMkAGM2MmZiMTcy(...)AA=" ChangeKey="EQAAAA==" />
      </t:Mailbox>
    </t:Attendee>
  </t:RequiredAttendees>
</t:CalendarItem>
</t:SetItemField>

After playing with various versions of the above XML, I found out that the only combination that will pass is one without the <t:ItemId/> tag.

My solution - which may be risky - (hard to tell due to lack of documentation) - was to nullify the Id property on all attendees before updating an event in Exchange. Verified that even without the Id, Exchange properly matches the attendee to an existing contact.

Any advise would be greatly appreciated!

[davster]

ItemId element is used ONLY for private DLs and contacts. It would typically be used in lieu of the other properties, not in conjunction with them. So you are correct – feel free to null out those ItemIds. We have to do matching for one-offs and directory contacts anyways since those have no ItemId equivalent.
From: Jakub Kaleta [mailto:[email protected]]
Sent: Friday, February 19, 2016 2:32 AM
To: OfficeDev/ews-managed-api [email protected]
Subject: Re: [ews-managed-api] Attempting to add appointment attendee results in error "Cannot use personal contacts as recipients or attendees" (#69)

I also encountered this problem. In my case the scenario was that I was updating an existing contact, with a modified list of attendees.
In my tests it occurred with Exchange 2010, but not with 2013 (on Office 365).

The offending attendee looked like this:

<t:SetItemField>

<t:FieldURI FieldURI="calendar:RequiredAttendees" />

<t:CalendarItem>

<t:RequiredAttendees>

<t:Attendee>

  <t:Mailbox>

    <t:Name>Test ([email protected])</t:Name<mailto:[email protected])%3c/t:Name>>

    <t:EmailAddress>[email protected]</t:EmailAddress<mailto:[email protected]%3c/t:EmailAddress>>

    <t:RoutingType>SMTP</t:RoutingType>

    <t:MailboxType>Contact</t:MailboxType>

    <t:ItemId Id="AAMkAGM2MmZiMTcy(...)AA=" ChangeKey="EQAAAA==" />

  </t:Mailbox>

</t:Attendee>

/t:RequiredAttendees

/t:CalendarItem

/t:SetItemField

After playing with various versions of the above XML, I found out that the only combination that will pass is one without the <t:ItemId/> tag.

My solution - which may be risky - (hard to tell due to lack of documentation) - was to nullify the Id property on all attendees before updating an event in Exchange. Verified that even without the Id, Exchange properly matches the attendee to an existing contact.

Any advise would be greatly appreciated!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/69#issuecomment-186161165.