Newer Version Available
ContentDocument
Represents a document that has been uploaded to a library in Salesforce CRM Content or a file in Chatter. This object is
available in API versions 17.0
and later for Salesforce CRM Content. The maximum
number of documents that can be published is 2,000,000. Archived
files count towards this limit and towards storage usage limits..
- Contact Manager, Group, Professional, Enterprise, Unlimited, and Performance Edition customers can publish a maximum of 36,000 new versions per 24–hour period.
- Developer Edition and trial users can publish a maximum of 2,500 new versions per 24–hour period.
Supported Calls
delete(), describeLayout()describeSObjects(), query(), retrieve(), search(), undelete(), update()
Special Access Rules
- Customer and Partner Portal users must have the “View Content in Portal” permission in order to query content in libraries where they have access.
-
Users (including users with
the “View All Data” permission) can only query files
they have access to, including:
- All Salesforce CRM Content files in libraries they're a member of and in their personal library, regardless of library permissions (API version 17.0 and later).
- All Chatter files they own, posted on their profile, posted on groups they can see, and shared directly with them (API version 21.0 and later).
- A Salesforce CRM Content document can be deleted if any of the following are true:
- The document is published into a personal library or is in the user's upload queue.
- The document is published into a public library, the user is a member of that library with the “Add Content” library privilege enabled, and the user trying to delete the document is the owner.
- The document is published into a public library that has the “Delete Content” or “Manage Library” permission enabled, and the user trying to delete the document is not the owner.
For API version
25.0 and later, you can change ownership of Chatter files and Salesforce CRM Content documents.
Note the following:
- To change ownership of a Chatter file, Chatter must be enabled.
- The following must be true to change ownership of a Salesforce CRM Content document:
- The Salesforce CRM Content app must be enabled.
- The user who is becoming the owner of the document must have a Salesforce CRM Content feature license.
- A user can change ownership of a Salesforce CRM Content document
or Chatter file if any of the following are true:
- The user is the current owner, or has either the “Modify All Data” or "Manage Salesforce CRM Content” permission enabled.
- The user has the “Manage Library” permission enabled for the library containing the document.
Fields
Usage
- Use this object to retrieve, query, update, and delete the latest version of a document, but not a content pack, in a library or a file in Chatter. Use the ContentVersion object to create, query, retrieve, search, edit, and update a specific version of a Salesforce CRM Content document or Chatter file.
- The query() call doesn’t return archived documents. The queryAll() call returns archived documents.
- You can’t add new versions of archived documents.
- If Chatter isn't enabled, Chatter files aren't included in query results.
- To query a file that is shared only with a record, you must specify the content ID of the file.
- To create a document, create a new version via the ContentVersion object without setting the ContentDocumentId. This automatically creates a parent document record. When adding a new version of the document, you must specify an existing ContentDocumentId which initiates the revision process for the document. When the latest version is published, the title, owner, and publish status fields are updated in the document.
- When you delete a document, all versions of that document are deleted, including ratings, comments, and tags.
- You can't create, edit, or delete content packs via the API.
- If you query versions in the API, versions with a PublishStatus of Upload Interrupted are not returned.
- A document record is a container for multiple version records. You create a new version to add a document to the system. The new version contains the actual file data which allows the document to have multiple versions. The version stores the body of the uploaded document.