10,853
edits
Salesforce admins: Urgent action required!
Synchronization steps: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 49: | Line 49: | ||
# First pass executes "easy" updates (all regular fields from all entities, and lookups - if possible). | # First pass executes "easy" updates (all regular fields from all entities, and lookups - if possible). | ||
#: If the update fails, we try to remove lookups and repeat the update. (Log: Update NoLookups for: account[...]) | #: If the update fails, we try to remove lookups and repeat the update. (Log: Update NoLookups for: account[...]) | ||
# | # The second pass executes status changes, owner changes, and lookup values that were not accepted in the first pass. | ||
The information about the upload process ends up in the synchronization log | The information about the upload process ends up in the synchronization log | ||
| Line 55: | Line 55: | ||
* If you enable sync details (using the [[Resco_Mobile_CRM#Setup|Setup form in Resco Mobile CRM app]] (parameter '''Diag. Sync Log''') or via Woodford), you will see all upload actions. | * If you enable sync details (using the [[Resco_Mobile_CRM#Setup|Setup form in Resco Mobile CRM app]] (parameter '''Diag. Sync Log''') or via Woodford), you will see all upload actions. | ||
;Upload Status with Data: When you enable this option in Woodford [[ | ;Upload Status with Data: When you enable this option in Woodford [[Data_model_in_mobile_apps#Managing_entities|entity configuration]], status changes for that entity are executed in the first upload pass. | ||
; (Salesforce) Force legacy batch upload API: Use the default option (in the [[Configuration#Salesforce|project configuration]]) unless you experience issues with APEX triggers or when recommended by Resco support. The default is faster and consumes fewer [[API calls]]. | ; (Salesforce) Force legacy batch upload API: Use the default option (in the [[Configuration#Salesforce|project configuration]]) unless you experience issues with APEX triggers or when recommended by Resco support. The default is faster and consumes fewer [[API calls]]. | ||
| Line 61: | Line 61: | ||
=== Result === | === Result === | ||
In optimal case, all changes are uploaded to the server. | In the optimal case, all changes are uploaded to the server. | ||
Some changes may fail to upload, due to: | Some changes may fail to upload, due to: | ||