To enable Salesforce Files, you must configure the two settings shown below. The first one setting is to include the actual objects that store the Content File information on Salesforce either with pulsar.sync.objects or with pulsar.sync.relationship.directives. The second one setting (pulsar.sync.cdl.objects) allows you to specify which parent objects that Pulsar should sync Files for. Modify your existing sync object list setting to include these objects as wellone of the following two settings depending on your setup. | Key | pulsar.sync.objects |
|---|
| Value | ...
ContentDocument
ContentDocumentLink
ContentVersion
... |
|---|
If you are using relationship sync directives instead, add these objects only at depth 0: objects| relationship.directives | | Value | ...
0 ; ContentDocument
|
0 ; ContentDocumentLink
|
0 ; ContentVersion
... |
Also specify this setting to sync files attached to specific objects. | Key | pulsar.sync.cdl.objects |
|---|
| Value | <object type list separated by commas or newlines> |
|---|
For example, to sync Files for Contacts and Accounts specify this value: Account
Contact
When using relationship directives in combination with this setting, a ContentDocumentLink directive will be automatically added (behind the scenes) for every directive where the target object type is one of the types in this cdl.objects setting (at the next higher depth). Also, subsequent sync stages will retrieve the ContentDocument and ContentVersion objects that are specifically referenced by the downloaded ContentDocumentLink objects.
| Note |
|---|
Specifying these two settings will sync the content records that the user can access, but will not automatically retrieve the actual file during sync. Depending on your requirements, you may prefer to have your users not pre-download all the files, but to download individual files on demand (network connectivity permitting). If, however, you require your users to always have access to the files, specify the base64 setting below. |
|