Classic Products
436 results found
-
3 votes
-
Indicate Honor/Memorial in dupe match for Tribute imports
When doing a tribute import it would be very helpful to indicate on the dupe matching form whether a constituent is already an Honor/Memorial as it helps to narrow down results when you only know their name.
3 votes -
Execute ImportOmatic programatically (eg from .NET code)
I realise we can use .NET code to execute IOM.exe (effectively simulating executing it from the command-line), but what would be even better would be to provide a proper .NET-based API for executing an ImportOmatic import profile. This would provide a much stronger automation option than either scheduling IOM.exe or executing it as a separate process - the calling .NET code would control when / how / with what parameters the import was executed, and could receive notification of the results either as a return value from the invoked method, or via the standard .NET exception mechanism - much better…
3 votes -
Update existing Ratings using the import ID
It would be very helpful to make this available to allow updaing the source value. We find duplicate ratings and need to change the source value to a different value. Using the import Id allows us to identify the exact record to update. We cannot rely on matching using the source and category.
3 votes -
3 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 -
Omatic data Service needs to follow Canada post standards too
Omatic data Service currently corrects addresses to USPS standards ONLY . So all our Canadian mailing addresses are adjusted incorrectly during import.
So I'm not sure why you would claim it corrects Canadian addresses when it corrects to the wrong format?? In Canada we follow Canada-post standards.2 votes -
Have FindOmatic pull up full List Management records, not just certain tabs.
When I search for a List Management record using FindOmatic, I'm not able to see all the tabs of information or edit all the information that I can if I access the record directly from List Management (adding notes, viewing actions, etc). It'd be great if these aligned so that I'd have the same access to view/edit a record whether I opened it within List Management or through FindOmatic. Right now we have to go through extra steps to look for a record in FindOmatic and then go over to List Management to find the same record there in order…
2 votes -
Ability to Change Existing Email Type to a Specified Type (i.e. Email 1, Email 2, Email 3)
Either change the "add existing phone/email as attribute to: **" option to "Add existing email as email type: **" and let us choose the appropriate email type OR allow users to do the inverse of "assign to next available number" and put the option as "Add the new value as new with the type identified and change existing email type to next available number."
2 votes -
Allow adding Benefits to existing gifts via IOM import
Currently, IOM doesn't allow you to update gifts with an import. I understand this for the core data on a gift (amount, fund, etc), but I think there should be an ability to update the "Benefits" section of an existing gift.
2 votes -
Add "Classy Mode %" and "Is Classy Mode" Fields to Import Profile
When importing transaction details from Classy to RE, it's important that service fee details (percentage rate and opt-in) are available to be added to the import profile.
If a client wants to track whether or not constituents opted to cover service fees and the percentage in service fees they covered in future RE reports, they are unable to do so because these import fields are unavailable.
2 votes -
Add on to comments during imports
When an import matches with an existing phone or email, add the possibility of having comments add to the end of existing comments instead of overwriting the comments completely.
2 votes -
Addresses for new records - add Date From date = system date
As new addresses are imported for new records, the Date From should be populated with the system date.
2 votes -
2 votes
-
Luminate Connector - Overwrite Existing Data with Blank or Null
We have been using the Luminate Online Connector for about two years and have recently noticed that when we have a two line address in Luminate that is updated with a one line address, the second line of the address is not overwritten with a blank to make the address correct on export. Only the first line is overwritten and the second line remains. So if we have an address like Line 1: Number 35, Line 2: 123 Sesame Street, and it is updated by Line 1: 567 Cherry Tree Lane, the update in Luminate ends up being Line 1:…
2 votes -
Notes about the profile
The description gives a brief description. We could do with a notes field to record more bespoke information about the profile. This could include changes need to import file before running import or any detailed information about the profile. We currently do this outside of ImportOmatic
2 votes -
Add the ability to import multiple Gifts with 1 profile
We have a .CSV file which splits Gifts out Merchandise Sales from Donations in different columns. It would be great if we could use the #number to add more than one gift on a single import. Then we could then assign a different Fund and an Appeal to each gift. At the moment we manually do this by creating separate spreadsheets and the use more than one profile, even though it arrives in one spreadsheet. Painful!
2 votes -
Allow duplicate Organisational Relationships without them being non-constituent
Raiser's Edge allows manual addition of relationships between the same constituents, with the same relationship and reciprocal types; this is useful for when people move within the same organisation as employees but have different positions. However, Importomatic does not allow this, either letting you import with a non-constituent as the link, or overwriting what it assumes is duplications.
https://iom.uservoice.com/forums/18118-importomatic/suggestions/4960907-duplicate-search-matching-results-add-add-as-new suggested a similar solution - I recently had to import historical data for student association memberships linking alumni to the organisation (so you can view the relationship from either side) with each cohort being recorded separately as the council is dissolved…
2 votes -
Add an option within VIP Processing to 'create exception' if a record meets the VIP query criteria
An added option to create an exception if a constituent record exists in the VIP query would be incredibly useful - especially when trying to avoid processing certain constituents (ex. Board Members) based on information that is in RE, but not in the incoming import data.
2 votes -
2 votes
- Don't see your idea?