Скачать или смотреть FLOW09: PART 3 HOW TO USE DATA TABLE IN SALESFORCE SCREEN FLOW || MULTI-SELECT IN DATA TABLE

The Data Table component in Salesforce Screen Flow allows users to view a list of records in a table format and optionally select one or more of those records. It's commonly used when you want users to take action on specific records from a list, like choosing Accounts to update or selecting Contacts to send emails to. You can give the component an API name (which must follow naming rules like starting with a letter, no spaces or double underscores), and a label that acts as the table title if you choose to display it.

To set up the table, you'll need to provide a source collection—a list of records, often retrieved through a Get Records element. You can also enable a search bar so users can quickly filter through the records shown. When it comes to selection, you have full control: you can allow single or multiple row selection, or even make it view-only. You can set the minimum and maximum number of rows that users must or can select, and preselect rows by providing a default collection. If you want to enforce that the user selects at least one row before continuing, there's an option for that too.

Each column in the table corresponds to a field from your object. You choose which fields to show and can set a custom column header label. You can also control how long text is displayed—either wrapped over multiple lines or clipped to fit in a single line. Note that fields from related objects (like lookup fields) won’t display unless you use formula fields to pull in that data.

You also have control over when the table is shown during the flow. It can always be visible, or only show under certain conditions you define using AND, OR, or custom logic. When a user selects rows, the flow can automatically store that data—either the first selected row or all selected rows. If needed, you can manually assign those selected values to flow variables.

Validation is also supported. You can add a formula to check the user’s input and show a custom error message if the validation fails. Plus, there are options to decide what happens when a user returns to the same screen later—either keep their previous selections or refresh the data based on updates made earlier in the flow.

Finally, a few key points to remember: The Data Table component isn’t mobile-friendly, supports up to 1,500 records, and users can select up to 200 rows. Search works across the entire dataset. Be careful when using formula fields, lookup fields, or fields with namespaces. Also, remember to manually add any used fields to your change sets when packaging the flow. If you're dealing with time zones, related records, or multi-currency fields, be sure to test thoroughly—some limitations may apply.

#Salesforce
#SalesforceFlow
#ScreenFlowSalesforce
#OmniStudioDataTable
#SalesforceScreenFlow
#DataTableComponent
#SalesforceDeveloper
#SalesforceAdmin
#LearnSalesforce
#SalesforceTraining
#VlocityOmniStudio
#SalesforceAutomation
#SalesforceBeginners
#SalesforceFlowBuilder
#SalesforceUI
#DeclarativeDevelopment
#SalesforceTips
#SalesforceCloud
#SalesforcePlatform