Lookup Fields in Flow

They have arrived with winter20. And they are tricky! Logging my initial thoughts and experiences to something I’ve been really wanting for years.

You can’t directly reference an object, like i want to do a lookup to campaign.

You have to reference an existing lookup field on a child object, like I want to lookup Campaign from Campaign Member, or I want to lookup Accounts on Opportunity.

As far as i can tell the end result is the same - you get the record ID, and you get the record name.

It looks like getting any other fields requires you to do a separate get records step, but thats easy enough.

See the image from the release notes - its looking up account from opportunity.

222_rn_forcecom_flow_fbuilder_lookup_builder.png

Here is a screenshot of my lookup to campaign

Screenshot 2019-09-27 at 12.09.34 PM.png

RecordId allows you to pass in a default value.

For more details, which Brian Kwong’s video here

My use cases
– i use a flow to create contacts, will be able to set the account on this instead of starting from the account
– same contact flow, will allow users to add to a single campaign

What I would love to see next
– the ability to select multiple records, like the ‘add campaign member’ functionality in lightning. add to collection, do stuff.

 
2
Kudos
 
2
Kudos

Now read this

Quirks with case and lookups in field references in visual workflow

I’ve been running into a number of bizarre issues with field references in flows. To illustrate these, I created a simple flow with a fast lookup to contact to an sobject variable named “sovContact” and a screen to display account... Continue →