Visualforce Developer Guide

Clouds with binary code floating aboveCloud with binary code floating above

No Results

Search Tips:

  • Please consider misspellings
  • Try different search keywords
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
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
Global Variables, Functions, and Expression Operators
Security Tips for Apex and Visualforce Development
Apex Classes Used in Visualforce Controllers
ApexPages Class
Action Class
Cookie Class
IdeaStandardController Class
IdeaStandardSetController Class
KnowledgeArticleVersionStandardController Class
Message Class
PageReference Class
SelectOption Class
StandardController Class
StandardController Constructors
StandardController Methods
addFields(fieldNames)
cancel()
delete()
edit()
getId()
getRecord()
reset()
save()
view()
StandardSetController Class
Execution Governors and Limits
PDF

addFields(fieldNames)

When a Visualforce page is loaded, the fields accessible to the page are based on the fields referenced in the Visualforce markup. This method adds a reference to each field specified in fieldNames so that the controller can explicitly access those fields as well.

Signature

public Void addFields(List<String> fieldNames)

Parameters

fieldNames
Type: List<String>

Return Value

Type: Void

Usage

This method should be called before a record has been loaded—typically, it's called by the controller's constructor. If this method is called outside of the constructor, you must use the reset() method before calling addFields().

The strings in fieldNames can either be the API name of a field, such as AccountId, or they can be explicit relationships to fields, such as something__r.myField__c.

This method is only for controllers used by dynamicVisualforce bindings.