File metadata sync
Metadata sync writes Salesforce field values onto the file in your storage provider, so the file carries its business context wherever it is read. This page is for administrators setting that up.
Configure a mapping
Section titled “Configure a mapping”Each mapping links one Salesforce field to one external metadata key, for a specific provider and object. Configure them from Storage Settings.
Supported field types are scalar values only: text, number, checkbox, date, datetime, picklist, phone, email and URL.
When metadata is applied
Section titled “When metadata is applied”| Provider | When |
|---|---|
| Amazon S3, Google Cloud Storage | In the signed upload headers, as the file is uploaded |
| Azure Blob Storage | As an update straight after the upload |
| SharePoint | On the backing list item’s fields |
Re-sync files already uploaded
Section titled “Re-sync files already uploaded”Use the Re-sync All action in Storage Settings for Azure Blob Storage and SharePoint when you need to push current Salesforce field values out to files that are already stored.
Google Cloud Storage needs its CORS rule to allow any request header for metadata sync to work from the browser. The rule in Configure CORS on the bucket already includes it.