Print Friendly and PDF

Salesforce: Implementing Parent Account Tagging Flow


This guide will go over the step by step on how to implement the Parent Account Tagging Flow inside Salesforce. 

The flow we will be building will follow the below diagram:


To review what the use cases of the Parent Account Tagging please see: Parent Account Tagging Use Case.


1) You must have the System Administrator Profile on your user or a profile that has the ability to access the 'Process Builder' and the 'Flow Builder' functionality.

2) We will be be creating the flow where the DU level will be the parent of the LS Matched. If you would like for the GU level to be the parent, substitute all areas that references DU for GU.


1) Navigate to Setup > In the Quick Find search for 'Flow'

2) Create 'New Flow'.

3) Drag over the 'Get Record' from the left hand side 'Toolkit' pallet 

Label: Find Parent Account

Description: Give description is you would like, this is an optional field.

Object: Account


Condition Requirements: Select 'Conditions are Met'




Select 'New Resource'

Resource Type: Variable

API Name: Child_DU_LSID

Data Type: Text

Availability Outside the Flow: Select both 'Available for input' & 'Available for output' 

Make sure to assign the variable that you just created in the Condition:


Sort Account Records

Sort Order: Descending

Sort By: LastModifiedDate

(This is if two account records with the same LSID to take the most recent record. Can also use 'CreatedDate' and take the newest or oldest as well).

How Many Records to Store

Select 'Only the first record'

Select 'Manually assign variables (advanced)' on the bottom.

Where to Store Field Value: Update 'In separate variables'



Select Variable to Store Account Fields

Field: Id (Account ID)


Select 'New Resource'

Resource Type: Variable

API Name: Parent_SFDC_ID

Data Type: Text

Availability Outside the Flow: Select both 'Available for input' & 'Available for output' 


Make sure to assign the variable that you just created in the Variable section

4) Connect the Start to the 'Get Record' widget

5) Drag over a 'Decision' widget from the left hand side palate.

Label: Parent Found

Outcome Details:

Label: Is Found

When to Execute Outcome: Select 'All Conditions are Met'

Resource: Select 'Parent_SFDC_ID' (the variable that was created in the Get Records)

Operator: Is Null

Value: GlobalConstant.False 

We know the Parent Account is found when we were able to find the SFDC Account ID.

6) Connect the Get Record widget to the Decision

7) Drag over an 'Update Record' widget

Label: Give it a name, example 'Update Child Record'

How to Find Records to Update and Set Their Values:

Toggle to 'Specify conditions to identify records, and set fields individually

Update Records of This Object Type:

Object: Account

Filter Account Records:

Field: ID (Account ID)

Operator: Equals

Value: New Resource

Resource Type: Variable

API Name: Child_SFDC_ID

Data Type: Text

Allow for Input and Output

Remember to assign the variable 

Set Field Values for the Account Records

Field: ParentID

Value: Select the variable that you created in the GET Records: 'Parent_SFDC_ID'

8) Connect all the widget. This will be for the 'Is Found' path.

9) Save, give you flow a name (ex: Parent Account Tagging Flow)

Type: Autolaunched Flow


Remember to 'Activate' the flow in the previous flow page

10) Now we will need to go to the 'Process Builder' and call this flow. In the Quick Search, search for 'Process Builder'.

11) Create a New process:

Name: LS Parent Account

Description: (Optional) - can give description of what this process does

The process starts when: Select 'A record changes'


11) Add Object

Object: Account

Start the process: Select 'when a record is created or edited'


12) Add Criteria: These are the Criteria for the Parent Account Tagging flow will trigger. I've listed the basic ones that, please feel free to add for any additional that are part of your business.

Criteria Name: Account Enriched

LSID Changed? TRUE



Parent Account Is Null? TRUE (we do not want to overwrite the Parent Account field 

LSID Does NOT Equal DU LSID (this prevents a Parent being a Parent of themselves)



13) Add Action

Select: Flows

Action Name: Execute Parent Account Tagging Flow

Flow: Select the 'Parent Account Tagging Flow' that you created above

Set up the flow variables for the 2 'Child' variables:

Child_DU_LSID Field Reference DU_LSID

Chid_SFDC_ID Field Reference ID (Account ID)


14) Activate

You have just setup the Parent Account Tagging Flow in Salesforce.

Please keep in mind that Process Builder Flows are in affect moving forward. To catch up your existing Accounts you will need to tweak the flow and add a 'Run Activation' field. 

If you have any additional questions or like to add a would like to tweak/enhance this flow such as in the absence of a DU LSID fallback to GU LSID or any other variation please reach out to us at


Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Please sign in to leave a comment.