BatchSave API DeDup automatically assigns constituents when it should show them as possible matches in the batch

When configuring batch options, users can choose how to handle potential constituent matches.  If you de-select the "Match records" option and select "Possible Matches" so that records are identified as a possible match if the match percentage is between 50%-100%, when the batch is saved, it will automatically assign a matched constituent instead of setting it as a "possible match."

If "Match records" is left selected, the possible matches will show up correctly.  

This problem also occurs if both options are de-selected.
Download and install the latest patch, which contains all fixes from previous patches. If you are running an older version, download and install the latest version and then the patch. 

Environment

 2.94.1524
 2.94.1524, patch 107 ; 4.0.138, patch 2

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.