If you implement Riva after disabling a different sync solution, Riva needs the ability to
- poll for appointment items in both the CRM and Exchange, and
- exclude creating or updating items that the previous sync solution has already synced between the CRM and Exchange.
Since Riva syncs appointments based on item start date, Riva needs to be configured to filter out appointments scheduled before a minimum start date.
With Riva sync policies, you will likely want to set a Sync Start Date/Time to capture contacts and leads from a considerable period in the past, for example, one calendar year. Riva would normally sync appointment items with start dates one year in the past. When Riva syncs those calendar items, it may create duplicate copies of calendar items that were already synced by the previous sync solution.
Example: You want to set a Sync Start Date for Jan 1, 2014, but need to set an appointment hard start date filter of August 31, 2015, because the previous sync solution will be disabled on August 31, 2015, and Riva will be enabled on September 1, 2015.
Custom Options
Riva now includes custom options that can be applied to the sync policy to set a hard minimum start date filter for calendar items. Once they are applied, Riva ignores any calendar item with a start date before the specified date. If a user creates or modifies a calendar item with a start date before the specified date, Riva ignores that calendar item and does not sync the new item or item update.
To apply the custom options:
- Set the following custom option keys against the sync policy:
Sync.Crm.MinStartDate = YYYY-MM-DD (sets minimum sync start date for CRM-to-Exchange)
Sync.Ex.MinStartDate = YYYY-MM-DD (sets minimum sync start date for Exchange-to-CRM)
Once the options are applied, Riva applies the minimum start date filter starting with the next full sync cycle for each user. This reduces instances of duplicating previously synced calendar items between the CRM and Exchange.
Applies to
- Riva for Exchange
- Riva release 2.4.30+