Sandy Fiddis
My feedback
65 results found
-
5 votesSandy Fiddis shared this idea ·
-
8 votesSandy Fiddis supported this idea ·
-
13 votesSandy Fiddis supported this idea ·
-
2 votesSandy Fiddis supported this idea ·
-
6 votesSandy Fiddis supported this idea ·
-
3 votesSandy Fiddis supported this idea ·
-
3 votesSandy Fiddis supported this idea ·
-
14 votesSandy Fiddis supported this idea ·
-
9 votes
An error occurred while saving the comment Sandy Fiddis supported this idea · -
12 votesSandy Fiddis supported this idea ·
-
54 votesSandy Fiddis supported this idea ·
-
166 votesSandy Fiddis supported this idea ·
-
4 votesSandy Fiddis supported this idea ·
An error occurred while saving the comment Sandy Fiddis commentedI already tried that but my query is over 190,000 records. Ideally I would still want to be able to see whether a record matched a deceased record - if the last gift date was before the deceased date then there is a chance they really are a duplicate.
Sandy Fiddis shared this idea · -
1 voteSandy Fiddis supported this idea ·Sandy Fiddis shared this idea ·
-
6 votesSandy Fiddis supported this idea ·
-
6 votesSandy Fiddis supported this idea ·Sandy Fiddis shared this idea ·
-
6 votesSandy Fiddis supported this idea ·Sandy Fiddis shared this idea ·
-
4 votesSandy Fiddis supported this idea ·
-
4 votesSandy Fiddis supported this idea ·
-
5 votesSandy Fiddis supported this idea ·
If I added a relationship manually, then they should no longer be considered duplicates - but in reality they will only be removed from the list if I clear the queue and rescan the database. Either remove them as possible duplicates when I scan just those 2 records or provide me a utility to remove all possible duplicates that have relationships to each other.