Salesforce admins: Urgent action required!

App projects: Difference between revisions

Jump to navigation Jump to search
1,101 bytes removed ,  27 January 2020
→‎Managing entities: moving description of the values of the On Conflict parameter to Conflict resolution
(→‎Managing entities: moving description of the values of the On Conflict parameter to Conflict resolution)
Line 153: Line 153:
:* Incremental with Sync Filter
:* Incremental with Sync Filter


; On Conflict {{Anchor|Conflict}}
; On Conflict: Conflict appears when the same record is changed on the device and before being synchronized, a change occurs on the CRM server (e.g. other user changes the same record and synchronizes changes before the first user, or the record is changed on the CRM server). See [[conflict resolution]] for details.
: Conflict appears when the same record is changed on the device and before being synchronized, a change occurs on the CRM server (e.g. other user changes the same record and synchronizes changes before the first user, or the record is changed on the CRM server). Select one of the [[conflict resolution]] strategies:
:* '''Server Wins''' – In the case of a conflict, the server version of the record is used and overwrites the record on the client. The action is noted on the sync log.
:* '''Device Wins''' – In the case of a conflict, the client version of the record is used and overwrites the record on the server. However, only the fields changed on the client are uploaded. If the changes on the server affected different fields than on the app, both changes are preserved. If the same field was changed in both databases, server values are overwritten.
:* '''Manual Action''' – Conflicts must be resolved, either by the user in the app or by an admin using [[Sync Dashboard]]. See [[Conflict_resolution#Configuring_conflict_resolution|Configuring conflict resolution]] for more information about the two options.
:* '''Device Wins (Full)''' – In this strategy, the whole record, including unchanged field values, is sent to the backend. So the whole record is used to overwrite the backend server version if the record, despite the server version of the record changes.


; Include Lookup Labels: When checked, the app no longer shows data related to that entity as “Unknown” in the offline mode. This often happened with ownerIDs of records, as the data with User names is stored in the User entity (by default the Owner entity is not enabled in Woodford).
; Include Lookup Labels: When checked, the app no longer shows data related to that entity as “Unknown” in the offline mode. This often happened with ownerIDs of records, as the data with User names is stored in the User entity (by default the Owner entity is not enabled in Woodford).

Navigation menu