You can use dynamic bindings to display field sets on your Visualforce pages. A field set is a grouping of fields. For example, you could have a field set that contains fields describing a user's first name, middle name, last name, and business title. If the page is added to a managed package, administrators can add, remove, or reorder fields in a field set to modify the fields presented on the Visualforce page without modifying any code. Field sets are available for Visualforce pages on API version 21.0 or above. You can have up to 50 field sets referenced on a single page. An sObject can have up to 2,000 field sets.
<apex:page standardController="Contact"> <apex:repeat value="{!$ObjectType.Contact.FieldSets.properNames}" var="f"> <apex:outputText value="{!Contact[f]}" /><br/> </apex:repeat> </apex:page>
Property Name | Description |
---|---|
DBRequired | Indicates whether the field is required for the object |
FieldPath | Lists the field’s spanning info |
Label | The UI label for the field |
Required | Indicates whether the field is required in the field set |
Type | The data type for the field |
<apex:page standardController="Contact"> <apex:pageBlock title="Fields in Proper Names"> <apex:pageBlockTable value="{!$ObjectType.Contact.FieldSets.properNames}" var="f"> <apex:column value="{!f}"> <apex:facet name="header">Name</apex:facet> </apex:column> <apex:column value="{!f.Label}"> <apex:facet name="header">Label</apex:facet> </apex:column> <apex:column value="{!f.Type}" > <apex:facet name="header">Data Type</apex:facet> </apex:column> </apex:pageBlockTable> </apex:pageBlock> </apex:page>
{!$ObjectType.Contact.FieldSets.Spectre__properNames}
Fields in a field set are automatically loaded when your Visualforce page uses a standard controller. When using a custom controller, you need to add the required fields to the SOQL query for the page. Apex provides two Schema objects that allow you to discover field sets and the fields they contain, Schema.FieldSet and Schema.FieldSetMember. For information about these two system classes, see “FieldSet Class” in the Lightning Platform Apex Code Developer's Guide.
Sample: Displaying a Field Set on a Visualforce Page
public class MerchandiseDetails { public Merchandise__c merch { get; set; } public MerchandiseDetails() { this.merch = getMerchandise(); } public List<Schema.FieldSetMember> getFields() { return SObjectType.Merchandise__c.FieldSets.Dimensions.getFields(); } private Merchandise__c getMerchandise() { String query = 'SELECT '; for(Schema.FieldSetMember f : this.getFields()) { query += f.getFieldPath() + ', '; } query += 'Id, Name FROM Merchandise__c LIMIT 1'; return Database.query(query); } }
<apex:page controller="MerchandiseDetails"> <apex:form > <apex:pageBlock title="Product Details"> <apex:pageBlockSection title="Product"> <apex:inputField value="{!merch.Name}"/> </apex:pageBlockSection> <apex:pageBlockSection title="Dimensions"> <apex:repeat value="{!fields}" var="f"> <apex:inputField value="{!merch[f.fieldPath]}" required="{!OR(f.required, f.dbrequired)}"/> </apex:repeat> </apex:pageBlockSection> </apex:pageBlock> </apex:form> </apex:page>
The order in which a developer lists displayed fields determines their order of appearance on a Visualforce page.