Loading

Error 'Can't Upload' on Attempt to Attach or Upload Files on a Salesforce Record

Julkaisupäivä: Jul 4, 2026
Kuvaus

Users may encounter the following error when attempting to attach or upload a file to a record in Salesforce Lightning Experience or a Lightning-templated Experience Site (Community):

"Can't upload FileName." followed by "Can't add 1 file to ObjectName."

When does this error occur?
This error is known to occur when:

  • Custom fields on the Content Version object are marked as universally required
  • Custom Apex Triggers exist on the following objects: Content Version, Content Document, Content Delivery, or Content Document Link
  • The organization has exceeded its file storage limit
  • Triggers associated with the ContentVersion object exist in a validation-type deployment that is active during regular working hours (this can cause a temporary disruption due to the org lock exception required for metadata integrity during deployments)

Note: In a community group, users may also see this error when trying to upload a file to an archived group. The only indicator that a community group has been archived is that the Chatter Publisher is missing.

Ratkaisu

Follow the steps below based on the most likely cause of the error in your organization.
Review Content Version Custom Field Requirements

  1. Navigate to Content Version from Setup:
    1. Salesforce Classic: Setup > Customize > Salesforce Files > Fields
    2. Lightning Experience: Setup > Object Manager > Content Version > Fields & Relationships
  2. Check the required fields in the list.
  3. Open each field in the "Content Version Custom Fields & Relationships" section by clicking the Field Label.
  4. If a field has "Required: Always require a value in this field in order to save a record" selected, uncheck it and save. If the field must remain required, consider implementing the requirement on the desired Content Version Page Layout(s) instead. See Customize Page Layouts with the Enhanced Page Layout Editor for details.
  5. Alternatively, if the custom field is a picklist and you use record types, set a default picklist value as a workaround. See Edit Picklists for Record Types and Business Processes for details.

Content Version Validation Rules can also generate this error. Navigate back to Salesforce Files (Classic) or Content Version (Lightning) and click Validation Rules. Temporarily deactivate or modify the validation rule to test.
If Apex Triggers Exist on Content Objects
Troubleshoot in a sandbox by marking the triggers inactive to test whether the error persists. See Disable a Salesforce Trigger in a Production Environment for more details.
If File Storage is Exceeded
Check File Storage and confirm it is at or below 100% capacity. Navigate to Data and Storage Resources for instructions. If the org has exceeded the limit, delete files or request a storage increase.
Related Issue — Private Chatter Group
If a user in a Private Chatter Group sees "Can't upload Filename" when dragging/dropping or selecting files from "Files", but is able to upload via the Chatter Publisher — log a Support case to enable "Content Delivery Setup."
If none of the above solutions resolve the upload error, create a Support case.

Knowledge-artikkelin numero

000381870

 
Ladataan
Salesforce Help | Article