Oracle CRM On Demand Desktop Administration Guide > How Oracle CRM On Demand Desktop Handles Oracle CRM On Demand Data > How Oracle CRM On Demand Desktop Handles a Shared Activity >

Example of How Oracle CRM On Demand Desktop Handles a Microsoft Outlook Meeting with Multiple Attendees

Figure 4 illustrates how user 1, who is a meeting organizer, creates a native calendar item in Microsoft Outlook and shares it. User 2, the invitee, accepts the invitation and also shares it.

Figure 4. How Oracle CRM On Demand Desktop Handles a Microsoft Outlook Meeting That Contains Multiple Attendees

The following process is performed:

1. User 1, the meeting organizer, creates a shared meeting with user 2, a meeting attendee who is a user.
2. User 1 saves the meeting and sends an invitation to user 2. The ConversationId is the same for the organizer and other meeting attendees.

   A ConversationId is the name of the field of Microsoft Outlook PIM items (Email, Appointment and Task) and is used to link a PIM item to an activity. When a PIM item is shared and a new related activity is created, the ConversationId field value is copied to the activity's iCRMId field so that both identifiers are the same. The activity's iCRMId is then synchronized with Oracle CRM On Demand as a part of the activity's field set. This synchronization makes it possible to link activities that are synchronized from Oracle CRM On Demand to PIM items.

3. User 1 synchronizes, and then Oracle CRM On Demand Desktop creates the activity on the Oracle CRM On Demand server.
4. User 2 receives and accepts the invitation.
5. User 2 shares the meeting, saves it, and then synchronizes. Oracle CRM On Demand Desktop determines user 1 already synchronized this Microsoft Outlook meeting with the Oracle CRM On Demand server because these items use the same ConversationId and include the same meeting organizer. In this situation, Oracle CRM On Demand Desktop identifies a duplicate during synchronization.
6. Oracle CRM On Demand Desktop detects that the activities are the same, and it then proceeds to perform deduplication conflict resolution without displaying an error message.