How to Sync Calendar Items (Meetings, Appointments, Events) in Salesforce¶
For users of the Email Sidebar on:
15 min read
Also refer to this article to learn about essential calendars sync exceptions and to this article for detailed information on how fields are matched between MS Exchange / Office 365 and Salesforce records
The general pattern of saving a calendar item (MS Outlook meeting / appointment / all-day event) depends on whether it is initial saving, on which the corresponding Salesforce event object is created or it involves updating / modifying of an existing event.
Initial saving is performed by Revenue Grid synchronization, therefore sync must be running when you are saving a new calendar item to Salesforce; however, updating / modifying an event object already existing in Salesforce is performed by the Add-In directly and immediately.
To prevent creation of duplicates of the same event, events deduplication is performed on server side during events syncing. Refer to this article for complete information about patterns applied with regard to attendees’ lists on Exchange → Salesforce and Salesforce → Exchange syncing.
In the latest RG Email Sidebar updates group (public) calendar events saving is also fully supported, it is performed in the same ways as saving of regular calendar events. At that, note that only 24 hours long or shorter events can be saved (due to a Salesforce limitation)
RG Email Sidebar also offers an on-demand possibility to link multiple Business Records to Events saved in Salesforce via RGES Sync; this function is not available in Salesforce out-of-the-box.
This feature requires Revenue Grid Salesforce managed package installation and can be enabled upon request.
Sliding time window limit¶
On saving calendar items, a two-level sliding time window limit is applied. This default limitation is implemented to prevent excessive API calls consumption and saving of irrelevant calendar items from mailbox to Salesforce.
The sliding time window ensures that relevant events are kept in sync over long periods of time, while also allows avoiding syncing very large amounts of irrelevant past events data.
RGES Sync only autosaves meetings and appointments which occurred no earlier than 14 days in the past from the present date. Older meetings are omitted from syncing, unless specifically saved by user.
Similarly, for future calendar items autosyncing the limit is 60 days in the future. Only calendar items scheduled to occur within 60 days from the current date are synchronized with Salesforce calendar.
For manual saving¶
Sliding time window limit for manual saving of calendar items applies only for Google and Office 365 mailboxes. Users of MS Exchange mailboxes can manually save meetings and appointments without any limits.
In RGES That is only the meetings and appointments that occurred no earlier than 15 days in the past from the present date can be manually saved to Salesforce by assigning the Salesforce category or using the Save button.
Sliding time window limit for manual saving of calendar is managed by the GoogleCalendarLastActivityTimeSpan setting for Google and by the ServiceCalendarLastActivity setting for Office 365. Refer to this article to learn more about other special admin settings.
If your company needs to manually save events that occurred more than 15 days in the past from the present date, submit a corresponding request to Revenue Grid support team.
Meeting / Appointment Autosaving¶
Autosaving of calendar runs according to the sliding time window limit described above. Only the meetings and appointments that are no older than 14 days are saved to Salesforce.
If the meeting auto-saving or appointment auto-saving switches are enabled in RG Email Sidebar sync settings, the Sync ending will automatically save in Salesforce respectively all meetings or all appointments which you create or accept (also tentatively accept) in email client.
Recurring calendar items can be synchronized automatically like any other items if Advanced calendaring is enabled in your Salesforce org. When a calendar item is autosaved, it will be linked to Related records retrieved for the item by RG Email Sidebar Initial Search. Calendar items which do not get autosaved are ones marked as private, internal (in-company) or blocklisted (e.g. personal) ones, and non-linked events.
It is possible to set up one-way auto-syncing of Salesforce Public (group) calendar events (presently only available in Salesforce Classic) with MS Outlook calendar; additionally, these events can be put into different event categories. Presently, this feature is enabled by request sent to our Support team; the request should contain a detailed description of your use case
Please also note that calendar items synchronization follows slightly different scenarios depending on whether internal or external contacts are involved and other factors.
Saving Calendar Items Semi-Automatically¶
Note if you need to save a new calendar item to Salesforce and RGES sync is not active for any reason, saving it is not possible until you enable RGES Sync. However, if a corresponding Salesforce Event record was created earlier, updating of its field values is made by the Add-In directly and does not require Sync to be running
Manual saving of calendar is performed with respect to the sliding time window limit described above. Only the meetings and appointments that are no older than 15 days are saved to Salesforce.
Calendar items can also be saved in Salesforce selectively in one of the following ways:
The category/custom folder calendar items syncing method is also handy when you need to save a calendar item from a stationary or mobile device if it goes offline for some periods of time (e.g. when losing wi-fi connection). Items saved in this way will be upsynced to Salesforce as soon as Internet connection is available.
In addition, this option can be effectively used to process multiple items
1. By assigning them the custom Salesforce category:
- click Categorize in MS Outlook ribbon and select Salesforce from the picklist
- or right-click the item and select Categorize > Salesforce
2. By clicking the Save button at the top of RG Email Sidebar for the calendar item opened in a separate MS Outlook window.
After you click Save, there will appear the Save current event as an Activity in Salesforce dialog:
In this dialog, you may change the primary record (a key Lead or Contact) that the Event will be linked to in Salesforce through WhoId relationship via the Name field or specify an additional Business record to be associated with it using the optional Related To field.
Either way, if it is initial saving of the calendar item, it will be saved in Salesforce on the next synchronization session; if the event object already exists, it will be updated immediately.
By default, internal (in-company) meetings (calendar items in which all attendees and the organizer belong to the same company) can only be saved in Salesforce manually using the described above procedures. However, there is also an Admin panel setting that allows saving internal events in Salesforce automatically; you can request that by sending us an email to our Support team. Additionally, please note that if an event’s attendees list contains only unresolved email addresses (ones having no Salesforce records associations), this event can only be saved in Salesforce after you create at least one corresponding contact association in Salesforce
Removing from Salesforce Calendar Items Synced by Mistake (Salesforce Unsync)¶
In the latest product updates it is possible delete (unsync) Events created in Salesforce by RGES sync. This function allows the users to easily remove an item synced to Salesforce by mistake, also in bulk. To remove a synced calendar item from Salesforce: assign it the custom “Salesforce Unsync” category in MS Outlook and wait for the next Sync session; that may take between 1 and 30 minutes.
>>> Click to see a screenshot <<<
Synchronizing Series of Recurring Items¶
Presently, there is a limitation on syncing of recurring meetings/appointments series if your are using Salesforce Lightning Experience: series of recurring calendar items created in Salesforce Lightning Experience cannot be downsynced to MS Exchange / Office 365 by RG Email Sidebar.
At that, series of recurring MS Exchange / Office 365 calendar items can be upsynced to Salesforce Lightning, but only as Salesforce Classic format events; therefore, they will be uneditable via Salesforce Lightning. As a workaround, you can temporarily switch to Salesforce Classic to edit them in Salesforce or edit them in MS Outlook and upsync the changes
If you need to save series of recurring calendar entries in Salesforce, please refer to this article to learn how to enable this possibility in Salesforce. In addition, recurring events saving needs to be enabled in RG Email Sidebar Admin panel; contact us to our Support team to request that.
Series of recurring events can be saved in one of the following ways:
1. In MS Outlook / Office.com, open the Calendar and right-click on an item which belongs to the series being saved, then assign it the custom Salesforce category
2. Double-click on an item which belongs to the series and select The entire series in the “Open Recurring Item” dialog window
Then, to get it saved in Salesforce, you can either assign the series the custom Salesforce category or open the Sidebar for it and use the Save button; in the latter case you can also choose specific Salesforce records to link the saved Event to instead of ones defined by RGES automatically.
The series will be synced on the following sync session.
Custom Salesforce Categories in MS Outlook¶
The following custom Salesforce categories are assigned to calendar items in MS Outlook to indicate their sync status.
Blue Salesforce category: item already saved or marked to be saved in Salesforce by sync
Red Sync Error category: item synchronization error. See this article to learn how to monitor and resolve sync errors.
Besides these statuses there are other colored categories assigned to emails and calendar items, which provide additional information, for example “Status: Tracked successfully.”, for items already saved in Salesforce, automatically through synchronization linked to pre-existing records or using the Save button, also for emails saved in Compose mode) or “Status: Required fields are missing: …” explaining a sync issue’s cause.
Note that in MS Outlook calendar view, items saved or marked to be saved in Salesforce by sync and items with synchronization errors are accordingly color-marked, so you can instantly tell their status:
Monitoring Events Synchronization Issues¶
Unresolved Meeting Participants¶
An unresolved meeting participant is one whose email address has no corresponding record registered in Salesforce.
When a meeting invitation is received from (or sent to) an unresolved attendee and then the meeting gets saved in Salesforce by the user and RG Email Sidebar finds no matching record to save the Event to, you will be prompted to create a corresponding record .
RG Email Sidebar can automatically create a corresponding Contact, Account, Lead, or opportunity record for unresolved meeting participants - refer to this article for more information on this feature. Contact Revenue Grid support team to enable this feature.
Continuous updating of meeting attendees lists¶
In the latest RGES updates the list of meeting attendees can optionally get re-synced with Salesforce on every sync session (previously, it was upsynced to Salesforce only once, on the meeting’s initial saving). That is required to get invitees added to the list later registered in Salesforce. This function is managed in RG Email Sidebar special settings, setting name SalesforceEventSmartAutoSharing.
Calendar Items’ Description Field Updating: Safe Description¶
There is one more important principle you should be aware of about syncing of meetings between your email client’s calendar and Salesforce calendar.
By default, when a calendar item’s syncing between your email client and Salesforce is performed by RG Email Sidebar, only its original body (description) is conveyed to Salesforce, and no future updates made in the description on either side are reflected on the other.
This principle is applied to prevent the cases when an end user would add some internal-use-only or sensitive notes to an event’s description in Salesforce – and without Safe Description applied these notes would be down-synced to the meeting’s description on email server and then automatically sent to all meeting invitees, along with any other meeting updates, potentially causing unwanted situations.
However, this principle does not apply to significant changes, i.e., the ones introduced to the meeting Subject, Assigned to field, and/or Start/End date/time in Salesforce after its initial saving to the CRM. In case of such changes, meeting notes are down-synced to the meeting’s description and thus become visible to the meeting invitees.
A suggested workaround in such situations is first to introduce the necessary change to the meeting Subject, Assigned to field, meeting’s Start/End date/time, wait for the meeting to sync or force sync it to Salesforce, and then update the meeting notes after the meeting’s synchronization.
If you prefer to disable application of the Safe Description principle for your entire Profile or for specific RGES users, send a corresponding request to Revenue Grid support team.
Combining Smart Description and Safe Description
Currently, combining Smart Description and Safe Description is supported only for MS Graph users.
For EWS, combining is not supported yet.
Saving Private Calendar Items¶
Please note that calendar items marked as private are never saved in Salesforce by RG Email Sidebar meeting/appointment auto-saving in the default configuration; however you can still save private calendar items manually by assigning them the Salesforce category or by using the Save button, provided you have the access permission (e.g when working with another user’s calendar via delegated calendars).
Customers may request private calendar items autosaving if their flow requires that, using the special setting ExchAutoTrackPrivateEvents.
Syncing Non-responded or Declined meetings¶
In the latest RGES updates, a special setting was introduced to manage the possibility to sync in Salesforce of inbound meetings which were left unresponded or were declined by the invitee (who is a RGES user). Some companies require that in order to get meetings registered in Salesforce even if they were not explicitly accepted. If this setting is disabled, an attempt to sync in Salesforce of a non-responded or declined meeting results in a sync error “ISE-013: Meeting for attendees cannot be synchronized until the organizer synchronizes it.“
Events Down-Syncing from Salesforce to Mail Client’s Calendar¶
If you create an Event or modify an existing Event directly in Salesforce, these Salesforce Calendar updates get automatically down-synced by RGES Sync engine: the corresponding calendar item will be automatically created or modified in MS Outlook or Gmail Calendar. Events modifications get to email client’s calendar within 1-30 minutes but new created Events get down-synced instantly.
However, if an event object is deleted directly in Salesforce, its matching MS Exchange / Gmail calendar item will not be deleted from mail client, it will only lose the Salesforce category / color coding.
Note that if a calendar item’s Organizer cancels it using the regular meeting / appointment / event cancelling procedure in MS Outlook, the corresponding Salesforce object will be deleted as well on the following sync session.
In the latest RG Email Sidebar updates a special high-level setting was implemented that allows to perform automatic Removal of calendar items from MS Outlook/Gmail calendar by RGES Sync if they were deleted from Salesforce Calendar
Smart Actions in RG Email Sidebar Opened for a Calendar Item¶
Meetings Sync Common Scenarios¶
The patterns of meetings saving in Salesforce vary in different situations depending on what kind of meeting participants are involved. Some of the common scenarios are described below:
1. The meeting organizer is an internal user (a user that belongs to your Salesforce org), i.e. a colleague from your organization. You are among the attendees, you have accepted the meeting and your meeting auto-saving is enabled; the organizer’s meeting auto-saving is not enabled. In this case the meeting will not be saved in your Salesforce until the organizer either saves the meeting in Salesforce manually, e.g. by assigning it the Salesforce category, or enables auto-saving. The corresponding “waiting for the organizer to synchronize the event” notification will be displayed in Dashboard Issues > Events
2. You are the meeting organizer. The meeting will be saved in Salesforce for you and for those of the attendees who are internal Salesforce users only if your meeting auto-saving is enabled or you have saved the meeting manually. In Salesforce, the corresponding event object will be linked to associated records of the attendees which are external contacts
3. The meeting organizer is not an internal Salesforce user (e.g. a colleague or contact that does not belong to your Salesforce org). In this case all meeting attendees which are internal users and enabled the auto-saving setting or saved the meeting manually will get the received appointment saved in Salesforce as its owners. It will be saved as an event Salesforce object linked to the relevant records of all external contacts involved (the organizer and some of the attendees).
This way, the event object will be linked to relevant records of all external contact attendees for as many times as many meeting participants which are internal Salesforce users (auto-)save the meeting, each of them indicated as the owner of this meeting. However, it remains the same single event object, since the meeting has one single MS Outlook GUID.
An example to clarify the scenario #3
For instance, there are four persons involved in the meeting:
IU1: an internal Salesforce user with meetings auto-saving enabled
IU2: another internal Salesforce, this one with event sync filters turned on but meetings auto-saving disabled
EU1: an external contact already registered in your Salesforce CRM
EU2: an external contact not yet registered in your Salesforce CRM
EU1 is the meeting organizer. EU2, IU1, and IU2 are the attendees. In this case IU1’s contact will be linked and added to the Activity History for EU1.
IU1 will be set as the meeting’s assignee in Salesforce. The attendees won’t be shown. In the default RG Email Sidebar configuration, the initial description from MS Outlook will be used in the event’s detailed view: ‘From:’ EU1 and ‘To/CC:’ EU2, IU1, IU2.
If IU2 saves the meeting in Salesforce by assigning it the Salesforce category in MS Outlook, Revenue Grid sync will create the meeting in the Activity History for EU1. In this case IU2 will be set as the event’s assignee in Salesforce.
Essentially, this way this event (with its specific MS Outlook GUID) will be duplicated. This is expected behavior, since sync is performing its regular patterns. At this point it is expected from IU1 and IU2 to negotiate who is going to be will be the event’s ultimate assignee, since there may be many attendees.
Calendar items which RGES cannot sync¶
• Ordinary MS Exchange / Office 365 All-day events which have a duration of over 14 days (a Salesforce limitation). A corresponding sync issue will be logged.
• Recurring Outlook All-day events and Salesforce Events which have a duration of over 24 hours. A corresponding sync issue will be logged.
• Any calendar items set in problematic time zones
• Calendar items outside out of the sliding time window, unless configured differently
Saving Calendar Items’ Attachments¶
In the latest RGES updates files attached to calendar items can be saved in Salesforce as Attachment objects, along with the items. Please refer to this article for more information.
Do more with RG Email Sidebar¶
Several key aspects of events syncing patterns can be fine-tuned according to your preferences via customization settings, Admin panel settings, or the extra settings managed by RevenueGrid Support team. Refer to the following articles to learn more about these possibilities: saving custom and standard Salesforce records as calendar items and one-way syncing; other on-request adjustments.
We would love to hear from you!