For example, your rules may miss situations where a contact has changed their last name - like for marriage or divorce - or email address. Matching and duplicate rules are powerful, but real data is complicated and your rules may not catch more complex duplicates. Make sure your users know about the rules’ criteria and ask them for feedback so you can fine tune as you go along. We recommend that you start by activating the default NPSP duplicate and matching rules, then add more if needed. Just like that you are one step closer to keeping user confidence in your data high and driving deeper adoption. (If you had to activate a clone of that matching rule, you need to change this setting to your new matching rule.) By default, NPSP uses the NPSP Contact Personal Email Match matching rule we activated a few moments ago. You can also select the matching rule to use (3).By default, NPSP alerts and reports the potential duplicate records on creation. You can also choose if you want to alert the user to a potential duplicate or report the duplicates either on create or on edit (2).By default, NPSP allows creation and editing. You can also determine if they receive an alert about the potential duplicate. You can choose to allow or block users from creating or editing potential duplicates with the Action On Create and Action On Edit settings (1).Click NPSP Contact Personal Email Match.Navigate back to the Duplicate Management menu in Setup and click Duplicate Rules.Now we need to activate the duplicate rule for what happens when a user starts creating a potential duplicate contact, account, or custom record. If your matching rule is locked in Activating status (a known bug that doesn’t allow you to activate this rule), click Clone, give it a memorable name, click Save, then click Activate. If this meets your needs, then click Activate to activate this matching rule if that option is available. The NPSP matching and duplicate rules have been designed to return the best possible set of matching candidates. In this example the NPSP rule matches on first name (fuzzy), last name (exact), and personal email (exact).To review the matching criteria, click on the NPSP Contact Personal Email Match rule.Click on Matching Rules under Duplicate Management.Enter duplicate in the setup Quick Find search box.Click the gear icon ( ), then click Setup.Let's take a look at the matching rule, create and edit a duplicate, and activate both. The NPSP matching rule matches on first name (fuzzy), last name (exact), and personal email (exact). Activate NPSP Matching and Duplicate Rules You just need to review and activate them. To get you started, Nonprofit Success Pack (NPSP) comes preconfigured with matching and duplicate rules. The matching rules are looking for records like each other, but not identical, to help you catch more potential duplicates. The term fuzzy in the context of matching means not exact. That means that Robert Alvarez and Roberto Alvarez would be identified as potential duplicate records. But you can also set up a rule to identify fuzzy matching for first names. Salesforce standard matching detects potential duplicate records based on exact matches, such as two contacts with the same name. Duplicate rules, the action that is taken when a user starts to create a potential duplicate.Matching rules, the criteria for finding duplicate records.Salesforce Duplicate Management searches for existing records upon creation and edit, then alerts the user and adds potential duplicates to a report. The good news is that Salesforce has a nifty tool that can help. Nobody’s perfect, though, and mistakes happen even with the best training. That means that training for your users is crucial! Be sure that your training materials encourage users to search before entering new contacts and accounts. Your best defense against duplicate contacts and accounts is to not create them in the first place, of course. Plus, that fundraiser may never trust your system again. While many donors might overlook the mistake, they may also wonder if their past contributions were really appreciated. What would happen if that fundraiser approached the donor as if they had never given? A new fundraiser looks at the record that says the donor never made a gift. Imagine this scenario: You have two contact records for a major donor in your Salesforce org. That’s a big deal for your organization’s efficiency and effectiveness in program management, fundraising, and communications. What’s the big deal about duplicates? Duplicate data results in unnecessary clutter, inaccurate reporting, and reduced efficiency. Prevent the creation of duplicate data.After completing this unit, you’ll be able to:
0 Comments
Leave a Reply. |