Q - What triggers the sync to DSS?
A - Marking the field DSS Sync: "Sync to DSS" will record for syncing to DSS. This field is found on the Session, Case and Contact.
...
Q: What causes the error "Case ID already exists"?
A. The error "Case ID already exists" means that the Case was already synced to dex and has an existing Case ID however the Case was resynced again but the Case ID has been deleted. When the batch case sync runs it will try to create an ID and populate the Case ID field that is blank or empty but because the Case ID has existed on the DEX already it will throw that error on the Case with the deleted Case ID that they are trying to resync.
...
A. This happens when the Session fails to sync to Dex due to a Client or Client Case-related Error in Session (e.g. PRIMARY SESSION PARTICIPANT IS EXCLUDED FROM SYNC. OPERATION HALTED. (Failed Client Sync: ‘Client ID') Failed Case Sync: ‘Case ID’ ) when you update the DSS Sync field to Sync to DSS in the Client or Client Case records to include them on the resync, Salesforce will then get the Error returned from Dex and populate it on the Client or Client Case’s-> DSS Sync Status (e.g. Failed: Sync to DSS) and DSS Sync Log (e.g. Due to the requirements of a case related to this client, Living arrangements is a required field. Please provide an answer) automatically upon Saving. So, upon Saving the records were populated where DSS Sync: Sync To DSS and DSS Status: Failed: Sync to DSS.
...
Common Errors when Syncing with DSS
...