For sync policies created in Riva On-Premise 2.4.46 or higher, see Calendar date filters for the Riva sync to CRM.
If a customer is implementing 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.
During the initial sync cycle, Riva will sync copies of items in the CRM to the user's Exchange mailbox based on the Sync Start Time value set in the sync policy.
Riva uses the following date values when performing the initial sync:
- Appointments: Riva uses the Start Date/Time of the appointment item. Riva will sync copies of calendar items with a start date/time on or after the date/time specified in the sync policy.
- Tasks: Riva uses the Due Date of the task. Riva will sync tasks with no due date and tasks with a due date set for on or after the date/time specified in the sync policy.
- All other modules: Riva uses the Modified Date of the item (the date the item was last modified in the CRM). Riva will sync all other items based on the date created or last modified (whichever is the latest).
In some cases, customers may need to prevent Riva from syncing changes to existing CRM items that were created or last modified before a specified date. This allows the customer to set a default Sync Start Date/Time in the sync policy to apply to all modules but set a different Sync Start Date/Time for specific modules, like calendar items.
Advanced Options
Riva includes advanced options that can be applied to the sync policy to set a different start date filter to ignore existing CRM items with a create/last modified date before the specified date value of the custom option key.
To set a different start date filter:
Custom Option Key |
Value |
Explanation |
---|---|---|
Sync.Crm.SyncStartTimeOverride.Contact |
2014-09-04 |
Date format is YYYY-MM-DD. This key is used to ignore any appointments in Exchange or Notes before the specified date. This key is looking specifically at the "Sync Start Date" of the Contact item. |
Sync.Crm.SyncStartTimeOverride.Lead |
2014-09-04 |
Date format is YYYY-MM-DD. This key is used to ignore any appointments in Exchange or Notes before the specified date. This key is looking specifically at the "Sync Start Date" of the Lead item. |
Sync.Crm.SyncStartTimeOverride.Appointment |
2014-09-04 |
Date format is YYYY-MM-DD. This key is used to ignore any appointments in Exchange or Notes before the specified date. This key is looking specifically at the "Sync Start Date" of the Calendar item. |
Sync.Crm.SyncStartTimeOverride.Task |
2014-09-04 |
Date format is YYYY-MM-DD. This key is used to ignore any appointments in Exchange or Notes before the specified date. This key is looking specifically at the "Sync Start Date" of the Task item. |
Sync.Crm.SyncStartTimeOverride.Case |
2014-09-04 |
Date format is YYYY-MM-DD. This key is used to ignore any appointments in Exchange or Notes before the specified date. This key is looking specifically at the "Sync Start Date" of the Case item. |
Sync.Crm.SyncStartTimeOverride.Opportunity |
2014-09-04 |
Date format is YYYY-MM-DD. This key is used to ignore any appointments in Exchange or Notes before the specified date. This key is looking specifically at the "Sync Start Date" of the Opportunity item. |
This advanced option should only be set for a first sync or a re-initialize Resync.
Example: Customer wants to set a Sync Start Date for Jan 1, 2011, but needs to set an appointment and task start date of August 31, 2012 (the date the policy is first enabled). Riva will ignore calendar and task items created or last modified before the specified date values. The following option keys and values would be set in the sync policy:
Sync.Crm.SyncStartTimeOverride.Appointment = 2012-08-31
Sync.Crm.SyncStartTimeOverride.Task = 2012-08-31