Classic Products
44 results found
-
Add Membership information in the Review Possible Duplicates window.
We want the record with the most recent membership to be the surviving record. If a membership is purchased as a gift, the constituent won't have a gift record so the "Last Gift Date" column is not a reliable indicator of when the constituents most recent membership expires.
I've adjusted the survivor scoring to give "Membership Transaction - Added Last" a lot of weight, but it would be so reassuring to be able to double check memberships on duplicates without having to open the records.
It'd be great if the columns in the Review window could include the fields:
Current…2 votes -
MergeOmatic
Find duplicates for Tributes who may have no address by searching individual relationships. My database contains a ton of duplicates that I found manually by comparing the names & address of relationships.
If you find matches then merge I would like an option to merge relationships and tributes (of the same type)
2 votes -
Don't suppress mailings and emails to surviving record
Currently if the non-surviving record is marked No Valid Address and/or Requests No Email, those boxes get marked on the surviving record even if the surviving record HAS a valid address and/or wants email. I'm choosing the survivor because it has better data and it's time consuming to go into each survivor to update these checkboxes. (This dovetails a bit with some existing requests but isn't mentioned specifically.)
1 vote -
Ability to alter match criteria further in MergeOmatic. Allow to match on first and last name fields only for those without addresses.
Ability to alter match criteria in MergeOmatic. Allow to match on first and last name fields only for those without addresses.
1 vote -
When merging - SSN should be saved as encrypted value in the note field, rather than unencrypted, when using MergeOmatic
When records that have a value in the SSN field are merged through MergeOmatic, the data that is in that field is saved in the note as an unencrypted value - posing a security concern. Please keep the value as an encrypted value or do not save the data in the note.
1 vote -
Allow the ability to identify spouses by coding and not consider them a duplicate match
Allow the ability to identify spouses by coding and not consider them a duplicate match.
1 vote -
Add SSN (social security number) as a display column option
Add SSN (social security number) as one of the column options to enhance comparison and researching ease. We use AlumniFinder for research of records and need SSN to determine if records are duplicates.
1 vote -
SORTING Option
Please add a sort filter to the columns for Merge-O-Matic. Especially the NAME and Email columns. When you have a page with 100+ potential records for review sometimes you're looking for a specific record and a sorting function would Alphabetize this for quicker search. Yes, there's a search field but in the 4 years we've used M-O-M it has never worked even when looking for a name that is clearly showing on the list. Thank you.
1 vote -
Duplicates Exclusions - add ability to search via either ID or name
Apart from the other idea of being able to export list of duplicate exclusions & adding a 'date', it would be really helpful to be able to search via donor ID or name in the Duplicate Exclusions screen. At the moment, you can only display the possible duplicates chronologically via the ID, but when you are dealing with a list of over 1K, it would be so much more efficient to be able to search a 'name' or specific ID so you don't have to scroll through the long list.
1 vote -
Link to open the survivor & merged record query
After merging is completed, the current link to open the Survivor & Merged records in the Merged Queue page does not work. It would be great if the link to the survivor & merged records query work, so it save you extra time of having to return to Raiser's Edge to open both queries. This is currently on the bottom left hand corner of the Merged queue after merging, but when you click on it, it does not open the record.
1 vote -
Allowing different phone types to be displayed
Currently it is only displaying the first phone type recorded on RE. So for a donor that have both a mobile and home phone, and the duplicate record only have a home phone, on the display screen, you will see the mobile for one record and a home phone for another record. Sometimes you do not have address for one of these records, so without opening the record to check if the home phone are the same, you can't be certain it is a duplicate.
1 vote -
Create a query folder in Raisers Edge so MergOMatic can save for the queries for surviving records and source records
It would be really helpful if MergOMatic can save the queries for the surviving records & source records in a specific query folder in Raiser's Edge, e.g. similar to where you can save the ImportOMatic exceptions.
1 vote -
Luminate Exceptions- Record should not Disappear from list
When a record cannot be merged and the error is due to LO, that record dissapears until list is closed and opened again. What a pain. The system should auto file them into another section " Exceptions" for later review. If I'm trying to merge a record and there's an exception, it's not always the case that I can remember the name/ID of that donor record.
1 vote -
Duplicate Exclusions - Add the Date excluded records Added to list
• This list should have a date column of when the two records were marked as “Not duplicates”. Over time you might end up with many in there, perhaps at some point you want to revisit and remove them from that group to be rescanned but not all of them… it would be helpful to have a Date and ability to filter so that the ones removed from group are from a specific date the work was done…
1 vote -
Duplicate Result List - Sorting Headers columns
When reviewing Duplicate Result List The header row should be Sortable. Even if the duplicates list has a score criteria it’s helpful to have the ability to sort everyone within that score in Asc/Desc order by e.g. Name, Constituent Code or Email headers ….
1 vote -
Make Key Indicator and Last Gift Amount Fields Column Options
-Key Indicator field should be included (yes a query could be created just for ORG or IND) but having the option there would be good if you want to work on merges for IND and ORG at the same time and easily identify them in the duplicates list
-Last Gift Amount would also be a helpful criteria to include along with the already existing Last Gift Date field
1 vote -
Merge RE:NXT data that is lost during RE merge functions.
Merge RE:NXT data that is currently lost during RE merge function.
1 vote -
Ability to change Review settings in the Setup section
I am having trouble viewing the Review screens because of my settings but I can't change the settings until I get into Review mode. I need to be able to change the settings somewhere else, like the Setup section
1 vote -
Expand how MergeOMatic can be used
I'd like to purchase MergeOMatic, but I need some additional functionality to help with the data clean-up needs we have.
I'd like to be able to use MergeOMatic to move single gifts from records when they are recorded on the wrong record.
I'd like to be able to use MergeOMatic to merge Spouse records. We merged a legacy system into ours which maintained spouses as constituents. Our process is to record them as relationships. It's cumbersome to take all the steps to merge these records.
I'd like to be able to merge Tributes. This is also a cumbersome process in…
1 vote -
New Layer to Approval Process
We have over 11,000 sets of duplicates in the "Duplicates to be Merged" Queue. We want to review the merges before they are actually merged but right now we can either merge ALL duplicates or a PAGE at a time. It seems impossible to review so many duplicates at one time and it is too time consuming to merge a page at a time.
We need another step where we approve the duplicates to be merged one more time (a page at time) then merge at the end of the day. If we could schedule these merges to take place…
1 vote
- Don't see your idea?