How is CRM Enhanced Sync different from a Regular Sync on VMobile Object Configuration Records?
Regular Sync updates an object’s records on the device if the record’s Last Modified By Date is after the Last Sync date. When Enhanced Sync is Enabled for a VMobile Object Configuration Record this will sync down all newly shared records regardless of the Last Modified By date and will remove all records and corresponding content/attachments to which the user no longer has access.
Use cases for this include the following:
- Enable for objects which have sharing rules configured (Except for Account and child objects of Account, which already utilizes Enhanced Sync by default)
- Enable when the WHERE clause on an object’s VMobile Object Configuration is updated. Disable after all users have synced down the change.
- Enable when an object is changed from a private share model to a public sharing model. Disable after all users have synced down the change.
- Sync times may be extended by enabling this feature - Only enable this feature for objects that require it
- Do not enable for VMobile Object Configuration records of type Related to Top Level. This will cause a duplicative sync and will extend sync times
- In a master child relationship, sharing rules are set only on the master object, but each child object which requires Enhance Sync, should have it checked on its VMobile Object Configuration record
- On CRM for iPad, if a user loses access to a record that they previously had access to, and the record was referenced via another record, this will cause sync errors. This behavior exists regardless if Enhanced Sync is enabled or not, but is noted here to provide additional clarity. (Exceptions are lookup to Account on Call2_vod and lookup to Key_Message_vod on Call_Key_Message_vod, which have special logic in place so the sync does not fail.)
- VMobile Object Configuration records do not need to be created for object share tables
- Enhanced Sync is only available for CRM for iPad and Windows 8 and 10
CRM Help Documentation: Using VMobile Object Configurations