How does Pulsar handle conflicts during the sync process?
- Carla Locke
Conflicts occur when different values exist for the same field in the Pulsar app’s mobile device database and the Salesforce server, such as:
Modifications made offline that differ from updates on the Salesforce server.
Overlapping changes from multiple users to the same record or field.
How does Pulsar prevent conflicts?
Pulsar sync is non-blocking, enabling users to continue working during the sync process. Pulsar attempts to prevent data conflicts by using a dual-database approach to manage data synchronization and resolve unavoidable conflicts. This approach includes:
UI Database: Users interact with this database for all read and write actions.
Sync Database: During synchronization, pending changes are transferred here before syncing with Salesforce. This ensures data consistency and prevents changes from being sent out of order.
Pulsar’s approach ensures updates are synchronized in the correct sequence, avoiding errors caused by out-of-order submissions.
What is Pulsar’s default behavior when resolving conflicts?
When Pulsar detects a conflict, it pauses the sync and prompts the user to choose whether to keep the device or server value. The conflict will remain unresolved until the next sync attempt if the user cancels the prompt.
Can I configure a conflict resolution policy to avoid user prompts?
Yes, administrators can configure automatic conflict resolution using Pulsar settings. At the object or field level, admins can set rules to always favor the device or server value. Conflicts are resolved silently without requiring user interaction when Pulsar is configured this way. For more information about configuring conflict resolution policies, refer to the following information in the Data Sync Settings section of the Pulsar for Salesforce Documentation:
What are the best practices to minimize conflicts?
Ensure regular syncs to reduce the likelihood of overlapping changes.
Use admin-configured conflict resolution policies for objects and fields prone to frequent updates.
What happens if conflicts remain unresolved?
Unresolved conflicts are re-evaluated in subsequent syncs. Pulsar continues to prioritize user input for conflict resolution unless an administrator configures automatic rules.