The new functionality within duplicate report is great. Love the option to permananetly remove a record as a potential duplicate.
Am missing the ability to base a duplicate report on a query. Ideally I'd like to run a report based on a query - as used to be the case - to prioritise those needing deduped first. I appreciate it can be sorted by new or old records and also that deceased and inactive can removed. For my purposes, neither of these settings really help me that much though. I also appreciate a longer winded way might be to export and paste the IDs into a new query and go from there, very lengthy though. Even having cons code as info in the report which could be sorted would help. As it stands a report takes some time to run and includes all records on our database so over 100k when I'm only interested in a particular cons code.
Would be great if this could be investigated as a potential improvement for future.
Thanks
See also https://re7.ideas.aha.io/ideas/RE7-I-350
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