To open, edit, create, activate or
deactivate a flow using all flow types, elements, and features available in Flow
Builder, including Einstein and Agentforce for Flow:
Manage Flow
Note You don't need to be an admin to have the Manage Flow permission. Ask your admin to add it to your profile or permission set.
Before you begin, understand the structure of your source and target data, such as whether the data contains multiple levels of collections within other collections. Mapping fields in a collection requires rules to preserve data integrity. See [Flow Element: Transform](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_transform.htm&release=264.0.0&type=5 "Select the flow resources for mapping and transforming source data to target data. You can use the Transform element in screen flows, autolaunched flows with no triggers, and record-triggered flows.").
1. Add the Transform element to your flow.
2. Edit the generated label and description if needed. Flow Builder generates them based on the element's configuration, and the API name populates based on the label.
3. Configure the source and target resources.
1. For Source Data, click the Add Resource button  and select the flow resource to transform the data.
Select a resource that references a collection to join. The resource can be an object that references a collection.
2. For Source Data, add another resource that references a collection to join.
3. For Target Data, click the Add Resource button  and select the data type.
Configure a resource that references a collection to store the combined data from the source collections. The resource can be an object that references a collection.
4. If the resource is a collection, select **Allow multiple values (collection)**.
5. For a Record or Apex-Defined data type, select the Apex class or object for the target data that the Transform element generates.
For example, if you specified that the target data is a collection and that the record data type is the Account object, the Transform element generates an account collection. If you didn’t specify a collection, the target data is a single account.
4. Map the source collections to the target collection.
1. Hover over a source collection and click the Map button .
2. Next to the target collection, click the Map button .
If a target collection doesn’t have the Map button , you can’t map to it.
5. Select join keys in the left and right source collections.
A join key is a field that uniquely identifies an item in a source collection. The join key in the left source collection corresponds with the join key in the right source collection. For example, to combine the orders, select the join keys that identify the same order in both source collections. The orderId field in the left source collection corresponds with the Id field in the right source collection. If more than one join key is required to identify an item in a source collection, add join keys.
6. Select fields to join from left and right source collections.
For example, select the SKU field from the left source collection because the right source collection doesn't contain that information. The combined data from the source collections provide a complete view of the order.
1. Click **Select Fields**.
2. Select the fields to combine in the target collection.
3. Click **Set Fields**.
7. Select target fields to store the values from the selected source fields.
1. Click **Select Joined Field Mappings**.
2. For each Target Field, select the field in the target collection to store the value of the corresponding source field.
For example, the SKU Number field in the target collection stores the value from the SKU source field.
3. Click **Set Mappings**.
8. Save your flow.
Example
Let’s create a flow that combines order records from an external order system with Salesforce orders to get a combined data structure that’s displayed in a data table in a flow screen. The flow screen shows each order along with the amount and the quantities.
Because the orderId field for the left source collection and the Id field for the right source collection identify the same order, we use those fields as the join keys. The join transformation contains 6 selected fields to join from the source collections. There are 3 mapped fields between the selected source fields and the target fields in the target collection.
Next in the flow, the Screen element contains the Data Table component that displays the combined data in the target output from the Transform element.
#### See Also
- [Transform Element](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_transform.htm&release=264.0.0&type=5 "Select the flow resources for mapping and transforming source data to target data. You can use the Transform element in screen flows, autolaunched flows with no triggers, and record-triggered flows.")
- [Data Table Screen Input Component](https://help.salesforce.com/s/articleView?id=platform.flow_ref_elements_screencmp_data_table.htm&release=264.0.0&type=5 "Display a collection of records in a table so that the user running the flow can select records. The flow stores the selected records as flow variables that the rest of the flow can act on.")