Classic Products
440 results found
-
Add as spouse within match screen
When IOM is proposing a match and you have the option to match to the "highlighted record" or "add new," a nice feature would be to "add as Spouse." Often, I find that IOM has matched to what is obviously the spouse's record. it would great if IOM would do it for you. Instead, I have to keep a list and then go match them up later.
2 votes -
allow you to search on only Preferred Address when looking for potential matches.
ImportOmatic should...allow you to search on only Preferred Address when looking for potential matches.
2 votes -
Seperate "Add New" and "Updated" No Valid Address
Be able to add an address with "No Valid Address" ticked.
Sometimes we get online donations from invalid or incomplete addresses from new donors, and would like to be able to add the address with the "No Valid Address" as ticked, but in the same import file, would want any updated addresses for existing donors that are updated to be unticked as "No Valid Address". Can this Constituent Default option be split out to give us the option of "for updated" addresses and "for new" addresses2 votes -
Automatically complete new BBDM constituent records
I'm currently having to manually load default sets into new constituent records when importing BBDM records. If there's a way to program Omatic to automatically apply Shift+F2 (loading default set) and then Ctrl+L (save and close), my life would infinitely improve!!!! Pretty please!!
2 votes -
import dictionary entries
You should be able to import a dictionary as an efficient way to update entries. You could export the current dictionary then make changes and import the new file into the existing named dictionary.
2 votes -
Include all the Tribute import fields
Currently fields are limited to: DateFrom, Darte to, Default Fund, Description, Honor/Memorial is an acknowledgee, Notes, Self acknowledgement letter, Tribute Type.
It would be beneficial to also include 'Gift ImportID', 'Gifts may be given', 'Tribute Notes', 'Consituent ImportID' and 'ConsiID'.
This way, one can link In-mem donors to their Tribute they're donating to, during the import. This prevents unnecessary duplication and presents the true support journey
2 votes -
Validation mode
Validation mode
It would be great if a default option could be available for 'Validation mode' which is present on the Import screen. The same for the 'Skip rows requiring user interaction'. Perhaps somewhere in the Configuration.
2 votes -
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 -
Add ability to import attribute categories only
Currently you are unable to import just an attribute category, a description must be included.
2 votes -
2 votes
-
Add ability to import Membership Renewal Schedule Information
It would be nice to be able to import pieces of the actual membership record, such as how often to renew, the card status default, and membership dues for the category
2 votes -
Avoid Accidental Matching
Add the option to only allow selections by mouse and therefore ignore keyboard entries during an import.
With a dual monitor set-up, I often check and respond to emails while running an import. If I happen to hit enter in my email when a match-selection window pops up on the import, it will automatically select whatever was highlighted. This has caused some accidental matches.
2 votes -
Add ability to direct output files to a different location.
Currently if you use the option to create Output files those files are written to the same location specified as the default, or to the location specified in 'Exception Files:". It would be helpful if these different file types could be written to different locations.
2 votes -
2 votes
-
allow for the updating of existing gift aid declaraton comments field
IOM does not currently allow the updating of the comments field on a gift aid import eg where we have had a batch of documents scanned & want to update the scanned documents exist indicator & also put a note in the comments indicating what file the scanned document is held in eg GA Scans Apr 2015
2 votes -
Expand options for joint membership card status
Please expand the options for membership card status to be imported or updated as Printed or Not Printed. The primary adult’s membership card is always changed to Not Printed when processing a renewal. Also the spouse and other relationship joint membership cards are being added as new cards and set to Not Printed, even though those cards already exist on the membership. We need all cards added and automatically set to Not Printed only if it’s a new membership. And we need to option to add new cards only if they do not exist and as Not Printed, but leave…
2 votes -
I was importing an email for a nonconstituent spouse and the email was not imported. Is there a way to capture this for the spouse?
I was importing a record with an email for a nonconstituent spouse and the email was not imported. Is there a way to capture this data for the spouse without overwriting the constituent's record?
2 votes -
Allow clients to point more than one csv file to one IOM profile during import process
When using other products like Sphere, the Sphere reporting is limited and may require clients to use mutiple data files (csvs) to build a single csv for IOM. It would be nice if IOM would allow clients to point more than 1 csv file to one IOM profile.
2 votes -
Dynamic dictionaries based on queries
Although ImportOmatic allows for record matching based on things like constituents IDs and Import IDs, sometimes it is useful to match on the an arbitrary value (e.g. within an attribute).
To get around this, we currently have a workflow which involves running and exporting a query, then copying the output into a dictionary. (In fact, we do this twice: once to match an attribute to a constituent import ID and once to match an attribute to a pledge import ID).
This whole process would be a lot smoother if dictionaries could be configured to pull directly from queries.
2 votes -
Warn when "copy field" is selected, but no seed has been specified
When working in the virtual field section, it doesn't make sense to specify that a value should be copied from another field without stating which field the value should be copied from.
Since all users are idiots (myself included), it might be quite useful if IOM flashed up a quick warning when "copy field" is selected as the function, without a corresponding value in the seed column.
2 votes
- Don't see your idea?