Potential Duplicate Notification template

Shalena Stelzig

I used the template from the MS power platform showcase and it seems to work really well. However, there are several records that are obviously not duplicates because the apartment number is different. Is there a way to limit potential duplicates and remove those when the address is completely different? It is set to strict search.

Stacy Cope

Hi @Shalena Stelzig! So glad it's helpful for you! On the apartment number issue, the flow doesn't do anything to evaluate matches, it just uses Raiser's Edge native search to try to find records with similar addresses. If false address matches are problematic, you could delete the address search steps from the flow entirely. You could potentially also do an evaluation in Power Automate where you compare the addresses and eliminate them from the digest if they are similar but not exactly the same. Either of these solutions would result in NOT getting a notification about two records with addresses “123 Main St” and 123 Main Street". I've found that every database has at least one apartment building where lots of their supporters seem to live, and when those pop up I would do a quick scan and mostly ignore them. So I would decide based on if it's more annoying to get the apartment building notifications and ignore them, or if it's more annoying to miss a potential address match. ?

I believe strict search applies only to names, but may be wrong about that, does anyone know for sure?