duplicate constituents

In 7.92, the algorithm for identifying duplicates is quite loose and retrieves far too many records that have little in common. The suggestion is to allow the duplicate report to run from a query so that each RE licensee can identify non-duplicate records and suppress those via query. A constituent attribute of “Do Not Merge” (Yes/No) allows users to identify records that clearly are not duplicates, such as multiple generations residing at the same address.

  • Guest
  • May 3 2013
  • Attach files
  • Guest commented
    March 18, 2016 00:12

    I am not sure I understand this suggestion.

    Attachments Open full size
  • Guest commented
    March 18, 2016 00:12

    Merge with the other similar "duplicate constituent" comments to consolidate votes to a single issue.

    Attachments Open full size
  • Guest commented
    March 18, 2016 00:12

    Add a unique identifier for suggestions so we can let you know to merge suggestion 101 with 307 because they are the same or similar. Sort matching search results in order of votes (descending) so we can see which have the most votes. Other posts similar to this one: The duplicate criteria algorithm is too broad and, therefore, brings up too many ' possible duplices when importing large volumes (22 votes); duplicate constituents (13 votes); Have an option to use duplicate constituent 7.92 criteria or specify your own criteria (377 votes); duplicate constituent report does not return true duplicates (26 votes); duplicate (15 votes); A much better duplicate search where you can create various criteria. Right now too many duplicates are not appearing in the report (12 votes); duplicate constituent search does not find true duplicates (4 votes) that over 500 votes to say the duplicate/merge tool is seriously inadequate and should get some serious attention

    Attachments Open full size

Related ideas