Integration with the Salesforce Content Version Object
FormTitan is an online web tool that allow you to create web forms and landing pages. The FormTitan form builder can easily integrate with salesforce content version object. Not only does this require no coding skills on your part, but the salesforce connector is seamsless and powerful. Unlike other products, our salesforce connector not only writes to your salesforce content version object but it can also read from it and populate your online form fields instantly. Furthermore, You can read from multiple objects at a time, with or without dependencies and query your objects based on any value from your form.
About the Salesforce Content Version Object
Represents a specific version of a document in Salesforce CRM Content or Salesforce Files. This object is available in versions 17.0 and later for Salesforce CRM Content documents. This object is available in versions 20.0 and later for Salesforce Files.The maximum number of versions that can be published in a 24-hour period is 36,000.
- Use this object to create, query, retrieve, search, edit, and update a specific version of a Salesforce CRM Content document or Salesforce file. Use the ContentDocument object to retrieve, query, update, and delete the latest version of a document, but not a content pack, in a library or a Salesforce file .
- Use this object to create, query, retrieve, search, edit, and update a specific version of a Salesforce file. Use the ContentDocument object to retrieve, query, update, and delete the latest version of a Salesforce file .
- To query a file that is shared only with a record, you must specify the content ID of the file.
- Not all fields can be set for Salesforce Files.
- You can only update a version if it is the latest version and if it is published.
- You can't archive versions.
- Using API version 32.0 and later, you can update record types on versions.
- You can't delete a version via the API.
- The maximum file size you can upload via the SOAP API must be less than 50 MB. When a document is uploaded or downloaded via the API, it is converted to base64 and stored in VersionData. This conversion increases the document size by approximately 37%. You must account for the base64 conversion increase so that the file you plan to upload is less than 50 MB.
- To download a document via the API, you must export the VersionData of the document. This does not increase the download count.
- When you upload a document from your local drive using the Data Loader, you must specify the actual path in both VersionData and PathOnClient. VersionData identifies the location and extracts the format and PathOnClient identifies the type of document being uploaded.
- SOQL queries on the ContentVersion object return all versions of the document. SOSL searches on the ContentVersion object return only the most recent version of the document.
- If you query versions in the API, versions with a PublishStatus of Upload Interrupted are not returned.
- Documents published into a personal library assume the default record type that is set for the user profile of the person publishing the document (General, if no default is set for the user profile).
Watch how it works