Occasionally the Normal Sync will not process, but you want your changed data to be pushed to the server anyway. This is an advanced setting, named Force Push Changes.

Where is the Force Push Changes setting?

The Force Push Changes setting is in the Settings menu under Advanced Settings.

Open

What does this setting do?

Force Push Changes sets a flag to tell Pulsar to push the local changes to the server, despite any issues which arose during the most recent Normal Sync. This allows the user to push local changes if they encounter any errors during the query modified stage (where it downloads updated records from Salesforce).

When does Force Push Changes work?

This setting only works when sync issues have been identified BEFORE the resolve stage of the Normal Sync (where local changes are pushed to Salesforce). If the sync issues are at or after the resolve stage, this setting will not work.

Why would you use this setting?

Sometimes, sync might fail due to a server restriction. For example, if Salesforce determines there are too many changes to send to Pulsar during a catch-up sync, then sync will return an error. If subsequent syncs continue to fail and there are still local changes to push, you can bypass that download updates stage to jump to the resolve stage that pushes those changes to the server.

What are the consequences of using Force Push Changes?

The consequence of using Force Push Changes will depend on the timing of the issues in the Normal Sync. The consequences include the following:

• Any possible field data conflicts may not be presented to the user for resolution because the corresponding server data may not have been downloaded to compare against. In this scenario, the local field change will always prevail and overwrite the server’s field data on the record.

• After successfully pushing your local changes, it is generally recommended that the user delete their account and resync their data especially if normal catch-up syncs continue to fail.