Salesforce Flow: Map Collection Support Roadmap

Upcoming map collection support in Salesforce Flow

Flow Builder has always had a single collection type, the equivalent of an Apex List, and the community has spent years asking for map-like data structures on top of it. Anyone who has had to manage key-value pairs or messier data relationships in a Flow knows the workarounds that gap forces you into.

The IdeaExchange history

The demand is easy to see on the Salesforce IdeaExchange. An idea opened in 2015, asking for the ability to use Maps in Flows, has over 1,300 votes and steady community comment behind it. The core request was a data structure like Apex's Map<Id, sObject>, with key-value storage and retrieval.

Salesforce's commitment and the new features

On July 21, 2026, Salesforce gave a positive update on the request. Direct HashMap functionality might not be the immediate priority, but Salesforce plans to address the underlying need with a set of new capabilities.

The features named:

• Get Related Records (GA). The feature is planned to reach general availability, giving you an efficient way to work with nested record collections without manual looping.
• A custom data type. Similar to Apex-defined types, but with no Apex code required, so you can build more sophisticated collection structures.
• Filtering and data extraction improvements. Builders would be able to extract related records from a collection and filter them on record fields or related child record fields, without writing custom loop logic.

Expected order of release (based on community insights)

Official timelines are still pending. The anticipated rollout order suggests a phased approach:

1. Easy related record extraction: retrieving related records from a collection without a loop.
2. Field and related record filtering: filtering collections on fields within records or their related children.
3. Custom data type support: the new, Apex-like type for advanced collection creation.
4. Get Related Records (GA): general availability once the earlier work simplifies nested collection handling.
5. Full HashMap support: dedicated HashMap functionality is expected later, since it was positioned as a lower priority than the rest.

What developers should do today

None of this has shipped, so keep using the workarounds and patterns you have. Keep a log of where you used them, so the migration is easier once the new Flow capabilities become available. Watch the Salesforce release notes and test each feature in a sandbox as soon as you can get at it.