When using a Flow, records can be automatically created based on the conditions specified. However, if the same conditions occur repeatedly, multiple records may be unintentionally created.
To avoid this problem, you can prevent the creation of unnecessary duplicate records by selecting “Skip matching record” in the “Confirm Matching Records” setting.
For example, consider a case where you wish to create only one opportunity, labelled “[Automatically Created] Opportunity”, for an account when the account’s “Rating” (API reference name: Rating) is changed to “Hot”.
If you do not use “Confirm Matching Records”, under normal flow settings, a new opportunity record “[Automatically Created] Opportunity” will be created each time the “Rating” of the account is updated to “Hot”.
Therefore, if the rating value is changed and subsequently updated back to “Hot”, the same opportunity record will be created multiple times, resulting in unintended duplicates.
This article describes how to prevent duplicate records from being created in such a flow.
Object: Account
Configure Trigger: A record is created or updated
Condition Requirements: All conditions are met (AND)
When to Run the Flow for Updated Records: Only when a record is updated to meet the condition requirements
Note: Enter an appropriate label and description. Although optional, best practice is to enter a description.
Label: Opportunity Creation
Description: * Enter an appropriate description.
How to Set the Record Fields: Manual
Object: Opportunity
Set Field Values for the Opportunity:
Condition Requirements: All conditions are met (AND)
Requirements Line 1
Requirements Line 2
If there is one matching record: Skip matching record
If there are multiple matching records: Skip all matching records
Contributor: Motohashi Takaaki | Trailblazer Community Forum Ambassador
Transitioned to the Salesforce industry after working for a heavy industry manufacturer. Has experience as a Salesforce systems administrator, in AppExchange customer success and as a consultant.
He gives a lecture in the Pathfinder DX personnel development program for the group preparing for the Salesforce Certified Administrator Examination.
He has hosted over 80 “Salesforce Saturday” Salesforce workshops since 2018.
He continues to communicate information on Salesforce through his YouTube channel with over 3,500 subscribers and his blog.
In first group of Trailblazer Community Forum Ambassadors. Is also active on the Salesforce Community Advisory Board (CAB).
Posted content reflects only the opinions of the user who made the post and does not represent the views of Salesforce. Regardless of whether a user is associated with Salesforce, posts may contain or consist of products, services, information, data, content, or other materials provided by third parties (hereinafter referred to as “Third Party Materials”). Salesforce does not manage, endorse, or guarantee any Third Party Materials (including their accuracy, validity, timeliness, completeness, reliability, consistency, quality, legality, usefulness, security, or applicable intellectual property rights), and assumes no responsibility whatsoever for them. Posts provided as answers to questions submitted via message boards or forums, or posts claiming to answer questions about Salesforce or its programs, are provided for general informational purposes only and should not be relied upon as answers to specific questions (even if an answer is marked as the “best” answer or similar qualifications are granted). For answers to specific questions, be sure to contact Salesforce Support. Salesforce has no control over posted content and assumes no responsibility for the use or misuse of posted content by third parties (including its distribution).
If you have any questions, please take advantage of the knowledge and expertise available in our Trailblazer Community at
https://trailhead.salesforce.com/trailblazer-community/feed
005056172

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.