--- schema_version: "1" id: f01542736de6f83fa9b72e0b79c365a0beb9d56722cfcdd80824284b1fedb015 title: Data Table Screen Input Component collection: admin version: current locale: en-us portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/flow_ref_elements_screencmp_data_table.md canonical_url: https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_screencmp_data_table.htm&release=264.0.0&type=5 source_site: help.salesforce.com content_type: documentation content_hash: 9dd47ff16964a57b27f41209fa9c29f77a377d90ca9f77f6f490a4ee054f366f description: Display a collection of records in a table so that the user running the flow can select records. The flow stores the selected records as flow variables that the rest of the flow can act on. products: - Flow Builder - Salesforce Platform release: "264" --- # Data Table Screen Input Component Display a collection of records in a table so that the user running the flow can select records. The flow stores the selected records as flow variables that the rest of the flow can act on. ### Required Editions
View supported editions.
## Configure the Data Table Name
Field Description
API Name

The API name of the component.

An API name can include underscores and alphanumeric characters without spaces. It must begin with a letter and can’t end with an underscore. It also can’t have two consecutive underscores.
Label If you select Use Label as the table title, the title text that appears preceding the component.
Use Label as the table title Indicates whether to show the label value preceding the table when you run the flow.
## Configure the Data Table Source
Field Description
Source Collection

For API version 65 and later, a collection of records or a collection of Apex-defined data types to populate the table.

For API version 64 and earlier, a collection of records that are used to populate the table.
Show search bar Enables users to search and filter their record results.
## Configure the Data Table Rows
Field Description
Row Selection Mode

Indicates how many rows the user can select in the table. You can set the value to:

Multiple
The user can select any number of rows between the Minimum Row Selection and Maximum Row Selection values.
Single
The user can select up to one row.
View only
The user can’t select any rows.
Minimum Row Selection Specifies the minimum number of rows that the user selects.
Maximum Row Selection Specifies the maximum number of rows that the user can select.
Default Selection Collection that specifies which records to preselect in the table.
Unique Identifier

Required. The field used to identify each record. The field requires a unique value for each record, such as an ID or API name.

To ensure your data table component works properly, provide a unique identifier. If you select a field that can have duplicate values, it can cause incorrect and unpredictable selection behavior, such as selecting multiple unintended rows.
## Configure the Data Table Columns To add the first column to the table, configure these fields. To add subsequent columns, click **Add column**. Drag the columns to reorder them.
Field Description
Source Field

Field from the Source Collection object to show in the column.

Fields with the anyType data type such as the NewValue field of the AccountHistory object are unsupported.
Display Options

Available only when the Source Field is a lookup field.

  • Show record name: Optional. Specifies whether to show the name of the related record instead of its Salesforce ID at run time. The option is selected by default.
  • Link to record: Optional. Specifies whether to make the name of the related record a hyperlink that opens the related record in a new tab. When you select Show record name, Link to record is selected by default. To make a record a hyperlink, select Show record name and Link to record.

If you select Show record name and deselect Link to record, the related record name appears as plain text at run time. Deselecting both Show related record and Link to record shows the Salesforce ID at run time.

Custom column label Indicates whether to display the column label value you specify as the column header.
Label If you select Custom column label, enter the text to show as the column header. Screen readers also read this text.
Default Text Overflow Mode

Specifies how text that is longer than the width of the column appears. You can set the value to:

Wrap Text
The screen shows the text on multiple lines.
Clip Text
The screen truncates the text to fit.
Let Users Modify Data Table

Allows users to modify fields in the Data Table at run time.

Sort column values
At flow runtime, users can sort data by clicking the column header.
Edit column values
At flow run time, users can update these supported record and Apex field types.
  • Boolean
  • Number
  • Currency
  • Phone
  • Email
  • Percent
  • Text
  • Text Area
  • String
  • Integer
  • Long
  • Double
  • Decimal
  • Id

When editing a field, users click Confirm to apply changes or Cancel to revert to the last confirmed value. If multiple rows are selected, users can update all selected items.
![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png) Note If you use a field that has a namespace, add the namespace to the beginning of the source field. For example, if your field's namespace is Acme, enter Acme\_\_FieldName\_\_c. ## Set the Component Visibility Specify the logic that determines when the flow displays the component.
Option Description
When to Display Component

Configure when the component is displayed by using conditional logic.

You can set the components to:

Always
Always display the component.
When all conditions are met (AND)
Display the component when all of the conditions that you define are met. Define at least one condition.
When any condition is met (OR)
Display the component when at least one of the conditions that you define is met. Define at least one condition.
When custom conditional logic is met
Display the component when the condition logic that you define is met. Define at least one condition and specify condition logic.
## Store the Data Table Component’s Values in the Flow The flow stores values automatically. If you store values manually, store the attribute’s output value in a variable. To store values manually, select **Manually assign variables (advanced)**. You can store all attributes in flow variables, but we recommend storing these attributes. | Field | Description | | --- | --- | | **First Selected Row** | First record in the table selected by the flow user. If a user selects two records, this record is the first selected record from top to bottom. | | **Selected Rows** | The list of records that the user selects. The records appear in order of their position in the table from top to bottom. | ![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_tip.png) Tip By default, screen components that run on Lightning runtime version 58 and prior have no memory. If a user enters a value, and then does one of the following, the value is lost. - Navigates to another screen and returns to the component’s screen. - Pauses the flow then resumes it. - Navigates to the next screen and triggers an input validation error. Setting the attribute enables a flow to remember the value. The flow stores the value automatically. If you store values manually, store the attribute’s output value in a variable. ## Validate Input Provide a formula that evaluates whether what the user entered is valid and the error message to display if invalid.
Option Description
Error Message Specify the error message that appears below the component if the user enters an invalid value.
Formula

Provide a formula expression that returns a Boolean value.

If the formula expression evaluates to true, the input is valid. If the formula expression evaluates to false, the error message appears below the component.

If the user leaves the field blank and the field isn’t required, the flow doesn’t perform the validation. If the user leaves the field blank and the field is required, the flow shows the default error message and not your custom error message.
## Specify the Behavior of Values on Revisited Screens Specify what this component does when a user enters a value, navigates to a previous screen, and then returns to the screen with this component.
Option Description
Use values from when the user last visited this screen The component retains the values that the user specified and doesn’t update the values to reflect changes made on previous screens.
Refresh inputs to incorporate changes elsewhere in the flow

The component updates the user-specified values to reflect changes made on previous screens.

If you pause and then resume the flow, the flow retains user-specified values only in Checkbox, Checkbox Group, Currency, Long Text Area, Multi-Select Picklist, Number, Password, Picklist, Radio Buttons, and Text components.
## Considerations - The Data Table flow screen component isn’t compatible with mobile devices. - If you use the Get Records flow element to retrieve the records to show in the Data Table, select **Choose fields and let Salesforce do the rest** for the best performance. - The maximum height of a Data Table is 400 pixels. - If you choose to wrap the text in a Data Table, make sure that the text doesn’t overflow when you test your flow. Wrapped text can overflow when a Data Table is compressed on a screen, for example, when it’s in one of multiple columns. - A Data Table can show up to 1,500 records. However, your search is performed on the entire dataset. - You can select up to 200 records in a Data Table. - If you apply a filter after loading your initial records, only the new results are shown. The initial records are no longer included in the display. - If a Data Table includes a formula field and records or updates to records that haven’t been committed to the database, the table doesn’t evaluate the formula properly. For records that don’t exist in the database, update the value of the formula field with an assignment using a static value or Formula resource. Doing so doesn’t affect any subsequent Create or Update operations in the flow. For existing records that have been updated, use an invocable action to reevaluate the formula, or use the IN operator to refresh the records and formula field values. - You can’t search the Time field. - The Subject field on Task and Event records isn't supported. - Dates and times are displayed in the International Components for Unicode (ICU) date and time formats. - In multi-currency orgs, the Data Table component doesn’t support records that are in a different currency from the user’s personal currency. - To display multilingual column header labels in the Data Table component, use the `$Label` global variable to specify custom labels. For more information about creating and translating custom labels, see [Custom Labels](https://help.salesforce.com/s/articleView?id=platform.cl_about.htm&type=5&language=en_US). - Data Table selections at runtime are subject to the client payload data limit described in [Lightning Aura Components Developer Guide](https://developer.salesforce.com/docs/atlas.en-us.lightning.meta/lightning/controllers_server_actions_call.htm). If you exceed this limit, the flow returns a generic error message. For example, if you include file data that exceeds the limit, the flow generates an error. We recommend avoiding fields like the VersionData field of ContentVersion records in your source collection. - If you have a flow open that has a Data Table component, and you update your user settings time zone on another page, refresh the flow page to show the updated date and time fields in the Data Table component. - When you set the row selection, be careful if you want to use the row selection of another Data Table component. Salesforce doesn’t support the use of row selections that have duplicate record variables without record IDs. - If you set the row-selection mode to single and make it required, or if you set the minimum and maximum row selection to 1, Salesforce uses a radio button at run time. Otherwise, we use checkboxes at run time. - If you package a flow that has a Data Table component, the fields used in the Data Table aren't automatically added to the package. If you use a field in the Data Table component, you must manually add it to the package. - Starting in API version 65.0, field name changes are automatically updated in Data Table components. For flows running in API versions before 65.0, if you rename a field in Object Manager that’s mapped to a column in a Data Table, Salesforce doesn’t update the column name. To see the new name in the Data Table, remove the column and then add it again. - Starting in API version 65.0, you can no longer delete a field referenced in a Data Table component. For flows running in an API version before 65.0, you can delete a custom field that a Data Table component uses. So, you must also remove the field from the Data Table component. - Starting in API Version 65.0, namespaces are automatically updated in Data Table components. For flows running in an API version before 65.0, if a Data Table component uses a custom object or custom field in an org without a namespace, and then later add a namespace to the org, you must also add that namespace to the associated column fields in the Data Table manually. - With column sorting, sorting doesn't impact the first selected row and the selected rows. - When you select **Show record name**, the sort and search options are unavailable. - Only when the user has access to the related record object, selecting **Show record name** shows the related record name at run time. #### See Also - [Use Multilingual Labels in Data Table Column Headers](https://help.salesforce.com/s/articleView?id=platform.flow_translate_use_multilingual_labels_in_data_table_column_headers.htm&release=264.0.0&type=5 "Add your translated column headers to the Data Table component using custom labels.") - [Data Safety When Running Screen and Autolaunched Flows in System Context](https://help.salesforce.com/s/articleView?id=platform.flow_distribute_context_data_safety_system_context.htm&release=264.0.0&type=5 "Screen flows and autolaunched flows without triggers can expose more data than intended. This potential issue primarily affects Experience Cloud sites accessed by external users. Configure proper user permissions for field-level and record-level security instead of running flows in system context. When system context is necessary, use only the minimum fields and records required.")