How to Map Values Using Global Flow Resources
Summary
Global Flow Resources introduced in Salesforce's Summer '26 release streamline value mapping by centralizing reusable mappings outside of individual flows. This feature makes it much easier to manage and update mappings across multiple flows without duplicating logic or consuming SOQL queries. It’s especially helpful when working with external systems requiring consistent data transformations based on predefined value mappings. Salesforce teams can now build flows that leverage these global resources for cleaner, more maintainable automation, particularly within Transform elements.
Takeaways
- Use Global Flow Resources to centralize and reuse value mappings across flows.
- Configure how unmatched source values are handled: default, fail, or pass through.
- Apply value mappings only within Transform elements in flows.
- Map external system field values to Salesforce fields efficiently without SOQL usage.
- Understand current limitations: not supported in before-save flows and not for collections.
Salesforce Flow is becoming more powerful with every release, but managing logic across multiple flows can still be challenging. One common example is value mapping. Until now, mapping values often meant building and maintaining the same logic directly inside each flow. In the Summer '26 release, Salesforce has added a new feature called Global Flow Resources. This feature lets you control value mappings outside Flow Builder. Using Global Flow Resources in the Automation app, you can create reusable mappings once and use them in any flow type that supports the Transform element. This makes it easier to manage mappings consistently across multiple flows. Value Mapping in Flow Value mapping is a common requirement in flows, especially when working with external systems. For example, you may need to map an external status value to a Salesforce Status field. For simple scenarios, you can use a formula with the CASE() function.