Sandy Fiddis
My feedback
65 results found
-
5 votes
Sandy Fiddis
shared this idea
·
-
8 votes
Sandy Fiddis
supported this idea
·
-
13 votes
Sandy Fiddis
supported this idea
·
-
2 votes
Sandy Fiddis
supported this idea
·
-
6 votes
Sandy Fiddis
supported this idea
·
-
3 votes
Sandy Fiddis
supported this idea
·
-
3 votes
Sandy Fiddis
supported this idea
·
-
14 votes
Sandy Fiddis
supported this idea
·
-
9 votes
An error occurred while saving the comment
Sandy Fiddis
supported this idea
·
-
12 votes
Sandy Fiddis
supported this idea
·
-
55 votes
Sandy Fiddis
supported this idea
·
-
168 votes
Sandy Fiddis
supported this idea
·
-
4 votes
Sandy Fiddis
supported this idea
·
An error occurred while saving the comment
Sandy Fiddis
commented
I 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 vote
Sandy Fiddis
supported this idea
·
Sandy Fiddis
shared this idea
·
-
6 votes
Sandy Fiddis
supported this idea
·
-
6 votes
Sandy Fiddis
supported this idea
·
Sandy Fiddis
shared this idea
·
-
6 votes
Sandy Fiddis
supported this idea
·
Sandy Fiddis
shared this idea
·
-
4 votes
Sandy Fiddis
supported this idea
·
-
4 votes
Sandy Fiddis
supported this idea
·
-
5 votes
Sandy 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.