Add an option to make it an exception to have multiple matches above the auto-match threshold

Currently if there are multiple matches above the threshold BVDL will automatically pick one as the match and continue on. This is not always desired and can complicate duplicate management.

We have several imports that we want to be update only. A.k.a if there is a match, then update, otherwise ignore for all record types.

We built a SQL based orchestration to implement this but a checkbox would be better!

This would also helpful for testing imports without creating any new records.

To allow for the best review of possible matched records, we set our exact match threshold very high. This is particularly useful when we are bringing in records with limited contact info but there are other data points we can use to enhance a match (alumni status or class year, donor interests, etc).

However, what we are left with are many records with either a single possible match or multiple possible matches but one obvious choice based on an enhanced match score that was applied by a pre-processing dynamic operation. The only way to turn such choices into an Exact Match is to open the form for every record, select the match, and save it.

It would be great to have either a record op on the Constituent Matching Results or an action for a staged data instance that allows inputs of a new Exact Threshold that can be run…

Currently if you try typing a space into the "Replace with" field, it just becomes a null value/empty field again. Incidentally it seems you can't even get around this using the =RegexReplace function because even inserting " " does not appear to work and replaces with a null value instead.