Appointments That Aren’t Synced in Bi-Directional Sync

These appointments aren’t synced in bidirectional sync:

• Appointments that are outside of a saved search
• Past appointments

Appointments Outside of Saved Search Aren’t Synced

Appointments that fall out of the saved search criteria set by the user or the administrator, aren’t synced.

Updates to Past Appointments Aren’t Synced

Appointments that have a start time or an end time before the sync job runs, aren’t synced between Outlook and the sales application, irrespective of the saved search chosen by the user. However, if a past appointment has a Shared with Oracle category, it is shared with the sales application but updates to that appointment aren’t synced.

Here’s a list of scenarios, where past appointments aren’t synced:

• Past appointments that were modified in the sales application or in the saved search aren’t synced to Outlook. The Shared with Oracle category isn’t cleared for the appointment in Outlook because the copy of the appointment still exists in the sales application.
  Note: The administrator gets an error message when a saved search that fetches past appointments is selected in Microsoft 365 designer.
• Past appointments that fall outside of saved search in the sales application aren’t synced. The Shared with Oracle category isn’t cleared for the appointment in Outlook because the copy of the appointment still exists in the sales application.
• Past appointments that were modified in the sales application and not in saved search aren’t synced.
• A past appointment that was already shared with the sales application and is modified later in Outlook isn’t synced to the sales application.
• A past appointment that is deleted in the sales application isn’t deleted in Outlook, however, the Shared with Oracle category is cleared because the appointment no longer exists in the sales application.
• A past appointment that is deleted in Outlook is not deleted from the sales application.