You are here:
Adding Record Fields to Flow Screens
Build flow screens faster by adding fields directly from your Salesforce objects. When you add a record field to a flow screen, its name, data type, help text, requiredness, and, in certain cases, existing values are automatically configured. Record fields use a record variable to determine which fields can be placed on a flow screen and their configuration.
Required Editions
| View supported editions. |
| User Permissions Needed | |
|---|---|
| To open, edit, create, activate or deactivate a flow using all flow types, elements, and features available in Flow Builder, including Einstein and Agentforce for Flow: | Manage Flow |
Place Record Fields Directly on Flow Screens
To add record fields to a screen flow, follow these steps.
- Create or edit a screen element.
-
On the Fields tab, select a record variable or create a variable with the Record data type
and the object that contains the desired field.
Alternatively, select a record variable automatically created by a Get Records element or a Loop element.
- From the list of fields that appear, drag a field to the screen canvas.
- To use a record field’s existing value, use a Get Records element for the record variable.
Record Fields on Flow Screens Considerations
Before you add fields from your Salesforce objects directly to your flow screens, consider record field behaviors.
Account Ticker Field
Placing the standard Ticker Symbol field on Account records in your screen prevents your flow from saving.
Creating and Updating Records
Just like other fields on a screen, record fields don’t save data automatically. To save the record field data, use the associated record variable in a Create Records or Update Records element.
Default Values
Record fields don’t support the default values of their source fields. If a record field’s source field has a default value, the record field is blank.
If the field contains a value in the record variable, that value is set in the screen at runtime as a default value.
Event and Task Record Fields
Some event and task record fields aren’t supported. The supported field types are Date, Date/Time, Checkbox, Number, Text, Text Area, and Text Area (Long).
At run time, event and task record fields behave differently on a screen than other types of record fields.
- Checkbox field labels aren’t shown in line with the checkbox. They’re shown above or below the checkbox.
- When edited, the record field doesn’t have a yellow background, and the undo button isn’t shown.
Lookup
- Creating a record from Lookup isn’t supported in these environments: Flows launched from URLs (such as List Buttons), Flow Debugger, Lightning Out, Digital Experiences (LWR), and Embedded Service Flows.
- Lookup fields aren’t compatible with mobile devices.
- To view or change the value of a Master-Detail relationship for existing records, the Allow reparenting setting must be enabled for that field.
- Lookup fields with filters applied don’t immediately display errors from the flow runtime when a user running the flow attempts to create a record. Errors display only when creating or updating the records that reference the newly created record.
- UI API must support the object where the Lookup resides.
Lookup Filters
If a lookup filter relies on the field values of the current record in the flow, fields used in the lookup filter must be added on the same screen. If you must limit the available records in your Lookup based on the actions taken by a user in a flow, use the Choice Lookup component.
Multi-Select Picklists
Using the Add Item operator in assignments allows for duplicate values in multi-select picklist fields.
Name Field
If the value of a Name subfield is changed at runtime, the new value is set, and the subfield shows the new value. But the full Name record field still shows the original value.
Permissions
System context doesn’t apply to record fields. If a user doesn’t have access to a record field, they can’t see it in a flow.
If no ID is set for the record variable, then the running user needs both Read and Create access
to change any record field values.
If an ID is set, the running user needs both Read and
Edit access to change any record field values.
In the record field details, the values in Update Compatible and Create Compatible reflect the properties of the field and your permissions. The values don’t reflect the permissions of the users running the flow.
Screen flows don’t display record fields that are set to read only at the object level.
Person Accounts
If PersonAccount is enabled and Account record fields have been added to a screen:
- When the record type is a Person Account, only Person* fields and common fields display.
- If the record type is a business Account, only Business account fields and common fields are displayed.
All account record fields are displayed and the record type is ignored.
The Account.Name displays as a PersonName field if the record type is a Person Account and
as a Text field if the record type is a business account. Account.Name displays as a Text field.
Picklist
Record fields support dependent picklists only if the dependent field is on the same screen as its controlling field.
If a record field has a record type ID set when entering the screen, its values are filtered by record type. If the record type ID isn’t set, all values are displayed.
Referencing Record Fields
You can’t reference record fields in other areas of your flow, such as formulas, decisions, and conditional visibility. Instead, reference the record variable that you used to create the record fields.
Runtime Environments
Record fields aren’t supported in screen flows on Experience Cloud sites that use Lightning Web Runtime (LWR).
Supported Field Data Types
Record fields support these field data types: Address, Checkbox, Date, Date and Time, Email, Lookup, Name, Number, Phone, Picklist, Text, Text Area, and Text Area (Long).
Other Considerations
- Record fields support object fields supported in the User Interface (UI) API.
- Record fields use the labels returned by the User Interface (UI) API, which can differ from the labels that appear on record pages and in Object Manager. For record fields of the Name data type, the label appears as Full Name instead of Name for most objects.
- Record fields aren’t supported in the Repeater screen component.
- Validating user input isn’t supported.
