Recommended
Showing an Apex Collection in a Screen Flow Data Table without a Custom Object (opens in a new tab)
You will learn how to define an Apex row type, return it from an invocable action and bind it to a Screen Flow Data Table with a Unique Identifier, avoiding helper objects.
Why read this
You will also learn the current limit that inline editing is not yet supported.
- Define row class with @AuraEnabled fields
- Return list from invocable action
- Store output in Apex-typed collection variable
- Bind to Data Table with Unique Identifier
Since Winter ’26 (API 65.0 and later), a Screen Flow Data Table can take a collection of an Apex-defined type as its Source Collection. Choosing a field as the Unique Identifier lets the table treat each item as a record, so users can select rows and the flow can reuse them. Display and selection work now, but inline editing for these collections is still pending.
The article contrasts this with older workarounds: creating a Custom Object that mirrors the Apex class, inserting and deleting temporary records, using a Transform element, or building a custom Lightning Web Component. Each works but leaves extra metadata to maintain. The walkthrough shows a sample FxRate class with @AuraEnabled fields, an invocable GetFxRates action that wraps the list in a result class, and the flow wiring that stores the output in a collection variable and feeds it to the table.
The author advises choosing a stable, unique key such as a record Id, an ISO currency code or a business key as the Unique Identifier, and generating one in Apex if the source has none. The pattern suits currency or stock quotes from an external API, financial calculations resolved in Apex, and batch results that should not be persisted.
Read the original at dev.to (opens in a new tab)