Visualforce Developer Guide

Introducing Visualforce
Tools for Visualforce Development
Getting a Quick Start with Visualforce
Customizing the Appearance and Output of Visualforce Pages
Standard Controllers
Standard List Controllers
Custom Controllers and Controller Extensions
Advanced Examples
Override Buttons, Links, and Tabs with Visualforce
Using Static Resources
Creating and Using Custom Components
Dynamic Visualforce Bindings
Dynamic Visualforce Components
Integrate Email with Visualforce
Visualforce Charting
Creating Maps with Visualforce
Render Flows with Visualforce
Templating with Visualforce
Developing Salesforce Apps with Visualforce
Salesforce Platform Development Process
Tell Me More: Where Visualforce Pages Can Appear in the Salesforce Mobile App Where Visualforce Pages Can Appear in the Salesforce Mobile App
Guidelines and Best Practices
Sharing Visualforce Pages Between Mobile and Desktop
Excluding Visualforce Pages from Mobile or Desktop
Creating Visualforce Pages That Work in Mobile and Desktop
Choosing an Architecture for Visualforce Pages in the Salesforce Mobile App
Optimizing the Performance of Visualforce Pages in the Salesforce Mobile App
Visualforce Components and Features to Avoid in the Salesforce Mobile App
Known Visualforce Mobile Issues
Access or Permission Issues
Device Sensor Issues
Input Issues
Loading and Performance Issues
Navigation Issues
Network Issues
Salesforce Classic vs. Lightning Experience Issues
Updating Records Issues
User Interface Issues
Considerations and Limitations for Using Visualforce in the Salesforce Mobile App
Prepare a Support Request for Problems with Visualforce Pages in the Salesforce App
Choosing an Effective Page Layout
User Input and Interaction
Managing Navigation
Introduction to the Salesforce Lightning Design System
Using Visualforce Pages as Custom Actions
Performance Tuning for Visualforce Pages
Adding Visualforce to a Salesforce AppExchange App
Using JavaScript in Visualforce Pages
Communicating Across the DOM with Lightning Message Service
Visualforce Best Practices
Standard Visualforce Component Reference
Appendices
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Updating Records Issues

These issues affect users trying to update records in the Salesforce mobile app.
Issue Solution
Users can’t save Salesforce records immediately after they have been updated. Instead, they see the error message "The record was modified by [current user] during your edit session. Make a note of the data you entered, then reload the record and enter your updates again". Avoid custom processes that remotely update a record before immediately invoking a standard edit page. Otherwise, users must wait 30 seconds, until the cache period has passed, before they are able to edit the record.
Collision detection is triggered when editing unread leads. The error message "This record was modified by (the user updating the lead) during your edit session. Make a note of the data you entered, then reload the record and enter your updates again" appears. Open the record and make changes using the edit button from the record detail page.
A recordTypeID error message appears when the optional recordTypeID parameter is omitted in the following command: sforce.one.createRecord(​entityName​[, recordTypeId]);. The error message “Review the errors on this page. Record Type ID: this value isn't valid for the user: [user name]" may appear. Modify the sforce.one.createRecord call on the Visualforce page to pass in the recordTypeId parameter.