New Collection Filter Criteria Resource simplifies Flow Builder data manipulation (opens in a new tab)
You will learn how the new Collection Filter Criteria Resource moves collection filtering out of the Flow canvas and into reusable resources.
Why read this
The piece explains how this change reduces visual clutter, optimizes governor limits, and enables in-memory sorting and filtering.
Collection Filter Criteria
- Configured via Manager tab
- Returns only first match
- Eliminates extra Loop steps
- Supports child relationships
Collection Filter and Sort
- Placed directly on canvas
- Returns full record collection
- Requires additional Loop steps
- Standard element configuration
Introduces the Collection Filter Criteria Resource as a Winter โ27 preview feature that shifts collection filtering from canvas elements to the resource manager. It replaces the traditional Collection Filter node, allowing administrators to define dynamic filter conditions and sort orders directly in memory without triggering additional SOQL queries or DML operations.
Explains the practical benefits, including cleaner Flow Builder canvases and optimized transaction limits. Multiple distinct filter views can now point to a single source collection, eliminating sequential logic and reducing visual complexity while speeding up execution across screen and autolaunched flows.
Covers advanced integration with Apex defined variables, noting that future updates will allow filtering based on child relationships within custom data structures. This capability aims to remove unnecessary loops during collection processing and hints at upcoming list and map functionality resembling native Apex collections.
Read the original at Salesforce Break (opens in a new tab)
Also told by Salesforce Admins Blog (opens in a new tab), Salesforce Time (opens in a new tab)