Admins / Developers / Flow

Salesforce Datatable Flow Component: Quick Overview

By Tim Combridge

The datatable component within Screen Flow is bound to be a crowd favorite. This is an out-of-the-box option for screen flows, currently in beta (as of Winter ‘23).

In this overview, we’re going to configure the component so that users can select multiple Lead records to convert. Let’s take a look.

Add a Datatable Component Within Screen Flow

1. Get Records: This flow will contain a “Get” collection. Here, I’m asking Flow to get all the Leads available in my org.

2. Datatable component: Add this after the collection, then give it an API name and a label (I’ve made mine descriptive: “Select Leads to Convert”). I’ve also ticked the box “Use Label as the Table Title” to keep everything consistent (say that ten times, fast!).

3. Source Collection: The “Get Leads” component that we created earlier.

4. Row Selection Mode: We’re allowing for multiple selection (multiple rows in the table), which means more than a single record can be selected in the table. You can also select “View Only” if you would like to simply display a table of data inside the screen flow.

5. Minimum row selection: This tells the component the minimum and maximum records to display at any one time.

6. Default selection: There’s no default selection because the purpose of this table is to select Leads to convert, so we don’t want to have a bunch of Leads showing by default.

7. Columns: Add which data points you’d like to be displayed to users when they launch the datatable.

8. Set Component Visibility (when to display the component): You may choose to restrict the component appearing by any criteria you desire, either user-attributed (e.g. by profile), or by field data (e.g. Lead status is “Contacted”).

9. Advanced settings: I’ve kept these as the default in this example, but you can change to “Refresh inputs to incorporate changes elsewhere in the Flow”.

10. Debug the Flow: Do this to simulate the users’ experience and check that everything is working as you’d expect. Then, ‘smoke test’ the component on the page itself, where the screen flow will sit.

Summary

The Datatable Flow Component is an out-of-the-box option for screen flows.

While the out-of-the-box Datatable Flow Component is not as feature-rich as the UnofficialSF component, it will cover a lot of basic functionality and enable businesses to display a datatable within a screen flow without having to install a third-party component.

The Author

Tim Combridge

Tim is the Managing Director at Sensible Giraffe, passionately educating others via high-quality blog content and training courses including the Ultimate Salesforce Flow Foundation Course.

Comments:

    Adam
    February 10, 2023 9:07 pm
    Have you encountered an issue with displaying dates in this table? I have an issue where the date shown is actually a day less than the date in the database.
    Jamal
    March 01, 2023 11:07 pm
    according to the help doc from Salesforce (https://help.salesforce.com/s/articleView?id=sf.flow_ref_elements_screencmp_data_table.htm&type=5), the Data Table component displays Date, Time, and Date/Time fields in UTC or Universal Time Coordinated time. Could that be causing your issue?
    Maria Gulino
    March 09, 2023 2:22 pm
    Same here! Has there been any solution to this?
    Eric
    March 09, 2023 8:43 pm
    Adam, i had this issue with a date formula. It seems to be due to the way SFDC stores dates as GMT. I found this on their site: Date and Date/Time values are stored in GMT. When a record is saved, field values are adjusted from the user’s time zone to GMT, and then adjusted back to the viewer’s time zone when displayed in record detail pages and reports. With Date conversions this doesn't pose a problem, since converting a Date/Time to a Date results in the same Date value. When working with Date/Time fields and values, however, the conversion is always done in GMT, not the user’s time zone. Subtracting a standard Date/Time field from another isn’t a problem because both fields are in the same time zone. When one of the values in the calculation is a conversion from a Text or Date value to a Date/Time value, however, the results are different. I was able to resolve my issue by changing to a real date/time field vs a formula.
    Justen
    April 27, 2023 6:55 pm
    Have you ran into an issue of putting two data tables on a screen flow and the second one not populating data?
    Rudresh Kumar
    May 02, 2023 11:10 am
    Since fields are directly taken from the Object, how can we make one of the column values as hyperlink, so that it can be redirected to detail page. Any ideas?
    Manuel Piquero
    May 16, 2023 5:44 pm
    The only way I could do this was to create a formula field on the object for the table and add that column Use this in the new formula field HYPERLINK( "/" & CASESAFEID(WorkOrderId), WorkOrder.WO_Number__c, "_self" )
    Barbara Martin
    June 28, 2023 1:57 pm
    #5 Minimum and Maximum not working to limit the number of rows displayed to the user on the screen. I read on another site that the purpose of minimum and maximum has to do with what the user must select, not display...I'm not there yet in my flow to check if the latter is true. Does anyone have a suggestion?
    Mazy
    June 29, 2023 6:19 pm
    I have the same problem :/
    Sohail
    June 29, 2024 9:47 pm
    How can I make the hyperlink work? I have a get record element on opportunity and I passed the collection record to the datatable. The name field of opportunity has the hyperlink by default but it is taking to the screen flow again not to the record detail page. Am I missing any steps? Thank you in advance

Leave a Reply