Salesforce Winter '26: Apex Collection in Screen Flow
Starting with Winter '26 (API 65.0), the Screen Flow Data Table accepts Apex-defined types without requiring custom objects.
Stock photo for illustration only, not from the actual event
- Native support for displaying and selecting Apex collections in Screen Flows.
- Eliminates the need to create extra custom objects or temporary workarounds.
- Fields must be marked with @AuraEnabled and flows require API 65.0+.
- Inline cell editing for Apex-defined collections is coming in a future release.
Since Winter '26 (API 65.0 and later), the Screen Flow Data Table component natively accepts a collection of an Apex-defined type as its Source Collection. By picking a designated field as the new Unique Identifier, the table treats each individual item as a standard record, enabling users to select rows and allowing the flow to reuse them seamlessly.
Juan Manuel Garrido, founder of EGA Futura and co-founder of Vantegrate, detailed this practical approach in a technical walkthrough on Dev.to, addressing a common workflow bottleneck for Salesforce developers who previously struggled to present Apex action outputs directly inside user interfaces.
This architectural enhancement significantly reduces technical debt within Salesforce orgs. Previously, developers had to provision temporary custom objects, utilize custom settings, or implement complex serialization to bridge Apex outputs with screen components. Relying on platform-native features ensures cleaner metadata and less maintenance overhead.
Every unnecessary object avoided means one less component to migrate, secure, or explain to incoming system administrators.
Previously, developers needing to display Apex action returns inside a Screen Flow had to resort to various workaround patterns that left lingering artifacts requiring ongoing maintenance.
Key requirements for implementing this feature include:
- Fields must be accessible to the Flow architecture, requiring the @AuraEnabled annotation.
- Flow configurations must target API version 65.0 or later.
- Current functionality supports viewing and selection; inline updates are pending.
Stock photo for illustration only, not from the actual event
"Display and selection work today; inline editing does not yet."
Juan Manuel Garrido
Inline cell editing for Apex-defined collections remains slated for a future platform release. If business logic dictates that users must edit inline values directly, separate input fields or a dedicated custom component should be utilized in the interim.
EGA Futura builds native ERP solutions on Salesforce, maintaining a strict engineering philosophy: leverage platform-native solutions before layering custom code on top to keep org environments lean and sustainable.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment