Skip to content

Historical Sync and Time Zone Matching

Office 365

Historical synchronization means inclusion of existing MS Outlook emails and events into SmartCloud Connect sync scope on the first start of SmartCloud Connect synchronization.

Existing events synchronization (historical sync) on SmartCloud Connect sync activation

After you a) install SmartCloud Connect, b) set up synchronization, and c) enable meetings/appointments auto-sharing, only those MS Outlook and Salesforce calendar items which are created after sync activation will be automatically synchronized between Exchange and Salesforce. Thus, the following categories of calendar items will not be auto-shared:

  • Any calendar items, including ones scheduled for any time after SmartCloud Connect sync initial activation but created before it
  • Series of recurring calendar items created before initial sync activation, including events scheduled to occur

Synchronization of such existing individual or recurring calendar items from MS Outlook can be initiated by the user - by assigning them the custom Salesforce category in MS Outlook, or using the Save button in the Sidebar.

Tip

If the existing events are too many to manually mark all of them for sharing in Salesforce through category assigning, you can order their inclusion into SmartCloud Connect synchronization scope as a separate custom service, by request sent to our Sales team.

Note

Please also note that SmartCloud Connect synchronization will not down-sync to MS Exchange/Office 365 your Salesforce calendar items which existed prior to sync initial activation.

 

Existing emails synchronization (historical sync) on SmartCloud Connect sync activation

After you a) install SmartCloud Connect, b) set up synchronization, and c) enable emails auto-sharing, SmartCloud Connect will auto-sync in Salesforce all your emails from/to non-blacklisted/internal addresses/domains sent or received within 6 days in the past from sync activation date.

Tip

The sync scope inclusion time span can be adjusted according to your needs by request sent to our Support team.

If you do not want to use auto-sharing for bulk syncing of your existing emails, you can initiate synchronization of only selected previously existing emails from MS Outlook, by assigning them the custom Salesforce category in MS Outlook, moving them to the Salesforce emails folder, or using the Save button in the Sidebar.

 

Times Zones Matching

The general principle how SmartCloud Connect syncs calendar items is integrating MS Outlook calendar items processing mechanisms and Salesforce calendar events handling, also matching their corresponding time zone-defined offsets. Additionally, when generating the time slots selection or calendar availability booking page, SmartCloud Connect reads the actual time zone values in recipients’ browsers and adjusts the scheduling table accordingly; a selector of other time zones is also included in the scheduling page.

Issues with uncommon time zones handling

Due to a discrepancy between the sets of time zones available in MS Exchange and Salesforce, some less common time zones cannot be matched properly on SmartCloud Connect calendar items synchronization. This results in synchronization issues of the following kind: Can’t match specified timezone: ‘Greenland Standard Time’ ({occurrence id}). If you encounter these issues, it is recommended to switch to a nearest matching commonly used time zone when working with SmartCloud Connect, if possible.

A detailed list of known problematic time zones:

MS Exchange/Windows time zone Salesforce time zone Status Details
Aus Central W. Standard Time - (UTC+08:45) Eucla n/a different
Central Brazilian Standard Time - (UTC-04:00) Cuiaba America/Santiago compliant unmatched DS period from Feb to May and ST start from Aug to Nov
Cuba Standard Time - (UTC-05:00) Havana America/Indiana/Indianapolis similar small unmatched period from 0:00AM up to 2:00AM for DS and ST start
Dateline Standard Time - (UTC-12:00) International Date Line West n/a different
E. Europe Standard Time - (UTC+02:00) Chisinau Europe/Athens similar small unmatched period from 2:00AM to 3:00AM for DS start and from 3:00AM to 4:00AM for ST start
Easter Island Standard Time - (UTC-06:00) Easter Island America/Mexico_City compliant matching is almost impossible - DS and ST switching is opposite
Greenland Standard Time - (UTC-03:00) Greenland America/Sao_Paulo compliant matching is almost impossible - DS and ST switching is opposite
Jordan Standard Time - (UTC+02:00) Amman Asia/Beirut compliant small unmatched period - several days on DS and ST start
Kamchatka Standard Time - (UTC+12:00) Petropavlovsk-Kamchatsky - Old Pacific/Auckland compliant large unmatched period for DS start from Mar to Apr and ST start from Sep to Oct
Mid-Atlantic Standard Time - (UTC-02:00) Mid-Atlantic - Old n/a different
Morocco Standard Time - (UTC+00:00) Casablanca Africa/Casablanca identical unmatched period from May to Jun in DS (floating ST for Ramadan)
North Korea Standard Time - (UTC+09:00) Pyongyang n/a different
Paraguay Standard Time - (UTC-04:00) Asuncion America/Santiago compliant very large unmatched period for DS start from Mar to May and ST start from Aug to Oct
Saint Pierre Standard Time - (UTC-03:00) Saint Pierre and Miquelon America/Sao_Paulo compliant matching is almost impossible - DS and ST switching is opposite
Samoa Standard Time - (UTC+13:00) Samoa n/a different
Sao Tome Standard Time - (UTC+01:00) Sao Tome n/a different
Syria Standard Time - (UTC+02:00) Damascus Asia/Beirut compliant small unmatched period for several days for DS and ST start
Turks And Caicos Standard Time - (UTC-05:00) Turks and Caicos America/Indiana/Indianapolis compliant large unmatched period for DS start from Jun to Mar
West Bank Standard Time - (UTC+02:00) Gaza, Hebron Asia/Beirut similar small unmatched period is only one day long for DS and ST start