Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

What is conflict recognition?

For Pulsar, the master system it is syncing against is the Salesforce platform. And the master time stamp
is the last successful sync time stamp. Pulsar has no knowledge of peer devices. A conflict iis recognized if the device is syncing to Salesforce and there is a new value on the Salesforce server since it last synced and the value has been changed on the device as well.

Conflict recognition example

If Field 1 on Record A is changed on the server and Field 2 on Record A changed on the device, there is no
recognized conflict. The sync algorithm would combine both changes and after it finishes, both device and
server would have updated Fields 1 and 2 on Record A

If Field 1 on Record A is changed only one one side (either Salesforce or device), there is no recognized conflict

If field 1 on record A is changed both on the device and Salesforce server since last sync time stamp, then a
conflict is recognized

  • No labels