Classic Products
438 results found
-
Checkbox For Show Exception Report
ImportOmatic asks if you would like to see an exception report, but not if Skip Rows Requiring User Interaction is checked.
Support said that option is for unattended importing.
Some of us use it as a quick-and-dirty means of importing.
It would be nice if a checkbox was included, so that we could choose to see that exception report.1 vote -
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 -
Have an option for the address similarity score to match only against the preferred address.
Since we save our addresses (even after NCOA) there are often a lot of same or similar addresses. Currently the advanced address processing window pops up for each transaction and we click ignore. It would be great if we could choose to base the address only on the preferred address and skip this process.
12 votes -
allow resolution of exceptions during the Import.
During import of constituent information, if the value in the Business/Industry field is not in our RE Table, the entire row is discarded as an exception. It would be very helpful to be able to resolve that conflict by adding the correct Industry value at that point, and moving on, and not losing the importing of the correct data that was included in the row.
7 votes -
13 votes
Phones and emails from which address?
-
Convert ZIP to city and state
Add ability (whether through Omatic Data Service or through API) to convert ZIP codes to a city and state.
1 vote -
Have the ability to share phone numbers between linked relationships who share an address.
Share phone numbers with constituents who have shared addresses.
4 votes -
1 vote
-
12 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 -
Skip a record when using Omatic Data Service
Omatic Data Service can take a long time for PO Boxes or if we missed a blank zip code field. Would like the ability to skip the record while in the middle of the process so we can continue without having to start all over again.
1 vote -
Speed the entering of record and value types when creating profiles
Selecting record and value types when creating a profile can be quite time consuming. I have four ideas that could potentially speed this up:
1) Have a button which attempts to guess record and value types based on field names. For instance, if I have a column headed "Gift Amount", it is highly likely that I'll want it to be stored as a "Amount" value within a "Gift" record.
2) Select multiple rows and set them all to one record type. Often data files will naturally be arranged with similar fields adjacent to one another. It would be really useful…
9 votes -
LinkedIn Connector (Bug Fix)
The LinkedIn Connector for AppOmatic has a bug when trying to log in with your LinkedIn credentials. It pushes out the error "Error logging in to LinkedIn. Please check your credentials and try again." though the credentials entered are correct.
2 votes -
Update former employer relationship and reciprocal fields
I would like to add the following functionality to Import-O-Matic: If an individual has a current primary employment relationship, and the
file I'm importing contains a new primary employment relationship, there should be a way to automate it so that the following steps are taken with
the old primary employment relationship:"Employee" check box is unchecked
Relationship and Reciprocal changed to "Former Employer" and "Former
Employee"
26 votes -
9 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 -
Allow Fund Relationships to be deleted
Blackbaud provides almost nothing to allow mass updates or deletes of Fund Relationships. ImportOmatic is our only hope. I hope this is possible. Please provide a way to delete Fund Relationships. I'm not fussy on how you implement this. I could either send you all of the fields on a fund relationship (fund ID, relationship, reciprical, date from, date to) or only the fund relationship import ID. We have several thousand fund relationships created in error an they need to be deleted, but our only option is to delete them manually.
2 votes -
system record id
IOM should be able to match Constituents by System Record ID.
2 votes -
Allow mapping of Import IDs for Timesheets
To help make sure I'm not importing duplicates, I'd like to be able to specify a Timesheet Import ID in my import file.
1 vote -
List Management command line export
We have made good use of the IOM command line capability to schedule and automate some of our Import and List Management processes. We would like to propose that the command line capability be expanded to include the ability to export lists from List Management. The would allow us to send list out for mailings or wealth screenings automatically and on a regular schedule.
1 vote
- Don't see your idea?