Attaching Salesforce Files on Mobile Devices
For Lightning-enabled users on mobile devices, files are automatically uploaded as Salesforce Files if they are attached to records via Attachments related lists or embedded (zvod) attachment fields for any object, including custom objects. To allow users to attach Files to records on mobile devices for custom objects, ensure each custom object has a unique Mobile ID field. See Administrative Do's and Don'ts for more information.
On the iPad platform, expense receipts attached to call reports are uploaded as Salesforce Files.
Configuring Salesforce Files Creation for Mobile Users
To allow users to attach files as Salesforce Files on mobile devices:
- Ensure VMOCs for the appropriate objects are active and the Include Attachments check box for each VMOC is selected. See Uploading Documents, Attachments, and Salesforce Files for more information.
- Select the Lightning Experience User check box on the appropriate User records.
- Grant users access to the VeevaOrgConfigurationService Apex class.
Additionally, in profile-based Chatter orgs, select the Enable Chatter check box for the appropriate user profiles to grant access to Salesforce Files. Admins can also use permission sets to enable this permission for a set of user profiles.
Managing Salesforce Files on Mobile Devices
For Lightning-enabled users who can upload attachments as Salesforce Files, the Upload Files button displays in place of the Add Attachment button on Attachments related lists and for embedded attachment fields.
Users can upload files up to 35 MB. If users try to upload files larger than 35 MB, an error message displays.
After attaching a file as a Salesforce File, users can perform the following actions from the More Actions menu, depending on the sharing settings of the File:
- Edit – Edit the description of the file
- Delete – Permanently delete the file from CRM
- Remove from Record – Detach the file from the record, but the file can still be viewed from the Files tab online
For a user to have access to the Remove from Record action, one of the following must be true: The user is the owner of the FileThe user has Collaborator access to the FileThe access permission for the File is Set by Record and the user has CRU access to the object to which the File is linked