Last Updated on February 5, 2025 by Rakesh Gupta

Big Idea or Enduring Question:

• How can I bring data from multiple sources into the data source using the Transform element and then map it to the target data source?

Objectives:

After reading this blog, you’ll be able to:

1. Utilize the Transform element to map and transform source data to target data.
2. Add multiple data sources to the source data.
3. Map fields from multiple data sources to a single target data source.
4. And much more!

Pre-requisites:

The first step is to carefully read and follow the instructions outlined in Transform Elements Over Loops: Create Tasks for Opportunities Without Loops blog. 

Business Use case

Warren Mason, a Junior Developer at Gurukul on Cloud (GoC), got a great idea about the capabilities of Transform Element after reading the articles below. He is confident that he can start using it for his next project.

1. Transform Elements Over Loops: A Modern Method for Collecting IDs in Salesforce Flow
2. Transform Elements Over Loops: Create Tasks for Opportunities Without Loops

Warren once again reached out to his mentor, Joe Smith, to ask if he could demonstrate how to add multiple resources to source data sources using a real-time use case.

Joe came up with an idea to enhance the automation we built for Transform Elements Over Loops: Create Tasks for Opportunities Without Loops. Currently, the newly created tasks are not associated with a contact. His idea is to associate these tasks with a contact (from the Account Contact Relationship object) whose role is Decision Maker. In his business, each account typically has one decision maker. If there is more than one decision maker, he wants to associate the task with the one who was created first.

Automation Champion Approach (I-do):

Joe plans to add new logic to the existing flow he created as part of the Create Tasks for Opportunities Without Loops. The enhancement involves the following steps:

1. Adding a Get Records Element: Add a Get Records element to retrieve the key contact who is marked as the decision-maker.
2. Utilizing a Second Data Source: Use the retrieved contact information as a second data resource within the flow. 
3. Mapping Contact ID to WhoId: Map the contact’s ID (retrieved from the Get Records element) to the WhoId field in the target data source. 

This approach enhances the efficiency and accuracy of the flow, enabling it to better address the business requirement of creating tasks tied to decision-makers for opportunities.

Guided Practice (We-do):

There are 3 steps to solve Warren’s business requirement using Record-triggered After-Save Flow. We must:

1. Clone the existing flow.
2. Add a Get Records element to find the decision-maker contact.
3. Update the Transform element to include a second resource for data source mapping.

Step 1: Define Flow Properties

1. Click Setup.
2. In the Quick Find box, type Flows.
3. Select Flows then click on the Flow Name that will be modified. In this case, Bulk Create Record Using Transform.
4. Click on the Save As New Version button at the top right of the Flow builder.
5. Click Save.

Step 2: Adding a Get Record Element to Find the Decision Maker Contact  

The next step is using the Get Element to find the decision maker contact. For this, we will use the Account Contact Relationship object.

1. On Flow Designer, click on the +icon below the Get Open Opportunities element and select the Get Records element.
2. Enter a name in the Label field; the API Name will auto-populate.
3. Select the Account Contact Relationship object from the dropdown list.
4. Select All Conditions Are Met (AND). 
5. Set Filter Conditions
   1. Row 1:
      1. Field: AccountId
      2. Operator: Equals
      3. Value: {!$Record.Id}
   2. Click Add Condition
   3. Row 2:
      1. Field: Roles
      2. Operator: Equals
      3. Value: Decision Maker
6. Sort Account Contact Relationship Records
   1. Sort Order: Ascending  
   2. Sort By: CreatedDate
7. How Many Records to Store:
   1. Select Only the first record
8. How to Store Record Data:
   1. Choose the option to Choose fields and let Salesforce do the rest. 
      1. Select Opportunity Fields to Store in Variable
         1. Id
         2. ContactId
9. Click the X at the top to save your changes.

Step 3: Update the Transform Element to Include a Second Resource for Source Data

Now we will update the Transform element to add a second resource for the source data. Then, we will map the ContactId to the Task WhoId.

1. Double click on Data Transform for Tasks transform element to open it on edit mode. 
2. For the second Source Data select {!Get_KeyContact}.
3. Map the ContactId (Second Source Data) to the WhoId (Target Data), as shown below.
4. Click the X at the top to save your changes.

In the end, Warren’s Flow will look like the following screenshot:

Once everything looks good, Click Save.

Almost there! Once everything looks good, click the Activate button.

Proof of Concept

To test this flow, I will update the Grand Hotels & Resorts Ltd account, which has four open opportunities, with Tim Barr as the decision-maker.

As per the logic we implemented in the flow, four tasks have been created, associating these tasks with their respective opportunities and decision-maker contacts.

Formative Assessment:

I want to hear from you!

What is one thing you learned from this post? How do you envision applying this new knowledge in the real world? Feel free to share in the comments below.