#Flow169 discussing

I recently implemented a Salesforce automation to simplify how we handle duplicate Prospect and Customer Accounts. Sharing the approach in case it helps other Salesforce Admins facing a similar scenario.

🔹 The Business Problem

In our process:

• Sellers manually create Prospect Accounts in Salesforce.
• Once a prospect becomes a customer, the Customer Account is automatically created in Salesforce through an integration with another system.
• The original Prospect Account remains in Salesforce.
• This can result in a Prospect Account and Customer Account representing the same company i.e, duplicate accounts.

Previously, sellers had to identify these duplicates and submit a ticket manually so an Admin could merge the records.

🔹 The Solution

I built an automation that follows this process:

Duplicate identified → Prospect Account flagged → Duplicate Account button + bell notification displayed → Seller clicks the button → Email sent to Service/Admin team → Admin reviews and merges the accounts

🔹 Implementation Steps

1. Create the Matching Rule and Duplicate Rule : A Matching Rule and Duplicate Rule to identify a Prospect Account and Customer Account as duplicates based on our internally defined matching criteria.

2. Create a Record-Triggered Flow: Record-Triggered Flow that runs when a Duplicate Record Set is created or updated.

Within the Flow:

• Get Duplicate Record Items: Retrieve the Duplicate Record Items associated with the Duplicate Record Set.
• Loop Through Duplicate Record Items: Loop through the Duplicate Record Items and assign the relevant Account/Company Name to a Flow variable.
• Find the Matching Account: After the loop, use Get Records on the Account object to find the corresponding Account based on the Account/Company Name stored in the Flow variable.
• Flag the Prospect Account: When the matching Account is found, update the Prospect Account and set our custom Duplicate Account checkbox field to True.

3. Display the Duplicate Account Button + Bell Notification: Duplicate Account button/action to the Account Lightning Record Page and configured Conditional Visibility based on the Duplicate Account checkbox.

When the checkbox is set to True, the seller sees the Duplicate Account button along with a bell notification. This gives the seller an immediate indication that Salesforce has identified the Account as a duplicate and that the records need to be reviewed/merged.

4. Notify the Admin Team: When the seller clicks the Duplicate Account button, an email is automatically sent to our ticketing system and Admin reviews and merges both Prospect and Customer accounts.

Here are screenshots of the flow:  

  #Salesforce Admin #Flow #Sales Cloud

🎉 Big shoutout to our incredible Forum Ambassador, @Manoj Nambirajan for an awesome deep dive on "Send Opportunity Notification for Specific Stage Movements"!📘 Check out the article here >> https://help.salesforce.com/s/articleView?id=005393369&type=1 

🔍 Found it helpful? Have thoughts to share?

 Let us know by clicking the "Yes" or "No"  button at the bottom of the article—your feedback helps us improve!> 🔍 Found it helpful?" style="display: block;" /> #Flow

I have a Flow that needs to send an email when a record is created on a Custom Object.  No matter what I put in the recipient field, I continue to get "0 recipients Error ID: 1728011022-505532"when I try to trigger the flow.  

What I first tried was go search resources, triggering record -> Respondent field (this looks up the contact) ->Contact ID:

When that failed, I tried several different versions of creating a text variable to look up the same thing and put that in the recipient ID field.  Again, no luck.  Finally, I switched the look-up from "Search Resources" to "Enter Text" and put in the text of a contact ID I know for sure is active and has a valid email address, but still got the error. 

For this flow, I need to have it pull the email address of the Contact (Respondent) listed in these records.  What am I missing? 

Howdy, 

I have a question about bulkifying scheduled flows. When you create one you have two options. Use a get element to grab the records you want or set an object & conditions. I've found the documentation confusing around which is the preferred method.

My understanding is that when you specify an object the flow will create an individual flow interview for each record. There is a limit of 250,000 flow interviews/24HRs along with all the normal limits. But if you have a sufficiently complex flow and expect it to pull in a large volume of records this is preferable as it prevents you from hitting nodes visited/DML limits.

In the case of using a Get statement, you don't have to worry about the flow interview limit, but you do need to worry about nodes visited/DML limits. Oh! And you get to work with collections! 

This makes me think that specifying an object is better for bulkification, I know there are other limits around date/time fields you can use in the criteria that might lead to one or the other, but from a pure bulkification best practices perspective specifying an object is correct?

Can anyone confirm my understanding or explain to me the correct way of thinking?

Additionally - in this help doc. There is the follow:

• The maximum number of schedule-triggered flow interviews per 24 hours is 250,000, or the number of user licenses in your org multiplied by 200, whichever is greater. One interview is created for each record retrieved by the schedule-triggered flow’s query.If you specify an object so that the flow runs for a batch of records, then set the time, frequency, and record conditions to avoid reaching this limit. You can use debug logs to check how many records a schedule-triggered flow runs on. Track the number of records with the FLOW_START_SCHEDULED_RECORDS event. If your org reaches the limit, Salesforce sends a flow error email.

This seems to indicate that specifying an object is the preferred method, but it's really confusing to me.  Also I'm not sure what it means by the "schedule-triggered flow's query"

Thanks in advance!