Sync Recurring Appointments

Recurring appointments can be shared with Oracle either using the add-in or when they're categorized as Shared with Oracle. However, updating and deleting recurring appointments follows certain rules.

General Tips and Behavior

Read these tips and behavior points to understand more about recurring appointments:

With appointment one-way sync, any updates or deletions of a shared recurring appointments from Sales aren't synced to Outlook. This is the standard behavior with one-way sync.
When a user shares a recurring appointment from Outlook, the entire series gets shared -- users can't share individual instances. A recurring appointment that starts in the past but ends in the future is still considered a future appointment.
The add-in doesn't allow sharing individual occurrences of a series. Users need to open the series to share it or use the Shared with Oracle category for sync to share the series.
For a recurring appointment series to be synced to Oracle from Exchange, it needs to have an end date. The end date needs to be within the maximum number of recurrences set in the profile option, Maximum Number of Appointment Recurrences (ZMM_ACTIVITY_MAX_RECUR).

Updates to Recurring Appointment Series or Individual Occurrences

This table presents the behavior in Outlook when bidirectional sync is enabled and a shared recurring appointment is updated:

Where Updated	Behavior of the Updates
All updates in Microsoft Exchange	Changes to the series or occurrences sync to Oracle Sales.
Oracle Sales when the series has past and future occurrences	Changes to the series sync to the series in Microsoft Exchange. Changes to a future occurrence of the series sync to the occurrence in Microsoft Exchange. Changes to a past occurrence of the series don't sync to the occurrence in Microsoft Exchange.
Oracle Sales when the series has only future occurrences	Changes to the series or any occurrences sync to the series or occurrences in Microsoft Exchange.
Oracle Sales when the series is completely in the past with no future occurrences	Changes to the series or any occurrences don't sync to the series or occurrences in Microsoft Exchange.

Deletion of a Series of Recurring Appointments

This table presents the behavior in Outlook when bidirectional sync is enabled and the entire series of shared recurring appointments are deleted from Sales:

Where Created	Series Has Start Date in the Past and End Date in Past or Future	Series Has Start Date in Future
Created in Outlook	The series isn't deleted in Outlook and the Shared with Oracle category is removed.	The series isn't deleted in Outlook and the Shared with Oracle category is removed.
Created in Sales	The series isn't deleted in Outlook and the Shared with Oracle category is removed.	The series is deleted in Outlook.

Deletion of an Individual Occurrence in Series of Recurring Appointments

This table presents the behavior in Outlook when bidirectional sync is enabled and an individual occurrence of a recurring appointment is deleted from Sales:

Where Created	The Deleted Individual Occurrence Is in the Past	The Deleted Individual Occurrence Is in the Future
Created in Outlook	The individual occurrence isn't deleted in Outlook and the Shared with Oracle category still appears.	The individual occurrence isn't deleted in Outlook and the Shared with Oracle category still appears.
Created in Sales	The individual occurrence isn't deleted in Outlook and the Shared with Oracle category still appears.	The individual occurrence is deleted in Outlook. The series it is part of remains the same and shared with Oracle.

Note: If a recurring appointment contains a custom field, only the first instance of the appointment is synced with the Sales application. The custom field needs an object trigger or a field trigger. Use the object workflows to update the custom fields in the recurring appointment.