Classic Products
438 results found
-
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 -
Add "Copy Existing Last Name to Maiden Name" button
When the "Compare Bio Field Value Changes" screen comes up, it shows the Import Value and the Existing Value of Bio 1 fields that don't match up. The Last Name import value is often the married last name, whereas the maiden name is the Existing Value. I wish there was a button to move Existing Last Name to Maiden Name. Right now, I have to click on the blue link to the record, and make the changes, but a 1-click solution would be great
4 votes -
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 -
Add another option for upper/lower casing names.
Some people's names don't follow the standard of capitalizing the first letter. Dick van Dyke for example. If you added an option that would look at a name and if the name already contained both upper and lower case letters skip it assuming that the upper/lower casing already present is correct.
6 votes -
Tribute Matching Adjustments
When importing tribute gifts, allow for more advanced tribute matching options. Currently, the only option is "match to existing tribute using tribute type". On our online platform, some of our donors create multiple "in honor of" tributes for the same person, e.g., "in honor of your wedding" and "in honor of your newborn". When we choose to match on tribute type and then import the data, these tribute gifts are put on the same tribute record. However, they should be on distinct tribute records. It would be helpful to match tributes based on other information, such as Description and Default…
3 votes -
Default Sets for Relationships
Importing relationships is an important function of IOM. When building an import file containing relationships, however, there are fields populated with redundant information that could instead be better represented through the use of a default set. Fields such as Relationship, Reciprocal, Date From, Print Position?, Primary,? and Employee? generally do not differ and end up containing identical information.
Furthermore, since the content or meaning of these fields is usually understood to be obvious simply by their existence in the import file, the original data file most likely will not contain these fields. That the individual is Employee of their Employer…
8 votes -
4 votes
-
2 votes
-
Allow you to import a file without a header row.
We have files provided from various sources and do not always have control over the format. In some cases these files do not include a header row, so the first row is actually data that we want to import. Currently IOM always treats the first row as a header, so it does not import data contained in the first row. It would be great if there was a checkbox in the profile configuration allowing you to choose if you want to treat the first row in your file as a header row or as a data row.
6 votes -
Import combined gifts from one line into sepearate gifts in batch.
It would be ideal that if recieving data that combines multiple gifts in one line on a CSV, IOM would have the ability to split this one large gift into several smaller ones with their own funds, campaigns and appeals.
1 vote -
Add option to export segmentation counts to Excel file
Team members working on a mailing often need the ability to review segmentation counts. These are displayed nicely in the segmentation results window, but there is no way to export this info and share with team members who do not have convenient access to SOM (except for screen capture). We would like to be able to share a full report of the segments, package assignments, and counts, at whatever state of assignment we have achieved, with our team members, preferably in an Excel file.
7 votes -
Add the option to place a dummy column before ImportID in modified resultant CSV
We experience a bug when importing the resultant CSV file through Raiser's Edge import (we do this for event participants to match the constituent we imported through IOM). The leading ImportID column has special characters in front of it on the CSV side and does not automatically match up to the RE field called ImportID.
Blackbaud was able to reproduce this issue and told us a solution was for IOM to add a dummy column to the resulting CSV before ImportID since this bug only affects the first column in a UTF-8 file. This happens in RE 7.85, and it's…
2 votes -
Add column to indicate annotations in matching grid
Add small column to indicate a record has an annotation in the matching grid. "Preview" annotation text by mousing over the icon.
1 vote -
Allow Deduplication to check List Management records
Some donations we process manually into batch, and not through importomatic. Hence would miss those records in List Management (as currently not using Findomatic)
Would be great to have MOM be able to dedupe on List Management data as well as RE Data1 vote -
1 vote
-
Ability to include non-constituent records for the records to be scanned
Currently, the records to be scanned have to be a full constituent. However, it would be nice to be able to run a list management list through to search for full constituent and other non-constituent matches.
1 vote -
For MailChimp Connector, add ability to load 'Cleaned' list member data
MailChimp assigns one of three status values to each email list member: Subscribed, Unsubscribed, or Cleaned. ImportOmatic enables me to import the Subscribed and Unsubscribed members, but I didn’t see an option to import MailChimp records with the “Cleaned” status even though the MailChimp API supports that. We have a constituent attribute in Raiser's Edge where we set the MailChimp status. Currently we have to update the 'cleaned' status using a file import.
3 votes -
Mailchimp Connector to import Multivariate campaigns
At the moment, the MailChimp Connector can only import campaign activity for standard type of campaigns.
Would really be useful if you can also include campaign activity for A/B test or Multivariate type of campaigns.
2 votes -
Add the ability to match only on MEMBER ID using Luminate Connector
We need spouses who share the same email addresses to be added to Luminate from RE in one import. Currently if the email is already on LO, it will update the wrong record and not add a new one even though we have LO configured to accept duplicate emails. To solve this issue we need import to have add/update logic based on MEMBER ID (RE ID) only
2 votes
- Don't see your idea?