We are starting to have quite a few import profiles (about 30) but most users only need access to 2 or 3 based on what they do here. It would be great to be able to restrict or mark which profiles show up for each user in the import processing list. That way they will not accidentally run an incorrect import and they won't have to scroll through a lot each time. To make it even sweeter it would be great to be able to set a default profile per user instead of for the installation as a whole.37 votes
There are a few ways we can address this issue, based on current and planned functionality in ImportOmatic. If you haven’t already done so, we recommend adding Tags to your profiles, which will allow users to quickly filter to the profiles they want to see.
However, we’re also considering the ability to restrict profiles to specific users. We would love to hear more comments on how your team divides responsibility for different profiles. Do the same people who run a profile also create it? Do multiple people on a team need access to the same profile, but not other teams? What’s your scenario?
Thanks, and we’re looking forward to hearing more feedback!
The Omatic Team
When merging records when one or both records exist in List Management, if the record deleted is the record in a list, the record gets removed from the list. All list assignments in List Management should be maintained when merging records regardless which direction the merge occurs.12 votes
IOM should have Last Gift Date as a column in the Duplicate Search Matching Results. If I am trying to figure out if 2 people with different addresses are really the same person it would help to know how long ago they gave their last gift.9 votes
Thanks for your feedback regarding our duplicate search columns! In addition to last gift date, would any other gift-related columns be helpful? For example – last gift amount, or total gift amount?
When we are interacting with the Membership from, we must resize columns with every pass to be able to distinguish different membership program names, etc. We adjust several columns to review, then when moving to the next record we have to resize columns again. Argh! Would be great if the column resizing "stuck" instead of requiring this same action over and over.6 votes
We do a daily three-pass import, and on Mondays we end up doing three imports (Friday, Saturday, and Sunday files). Since we end up with so many files (9 imports, and an exception file and an update file for each=18 files), it would be helpful if we could pick the exceptions/updates folder whenever we run the import. This way, we could keep each daily import in a separate folder, and run multiple imports concurrently. Right now, the exception and update files are named with the import time, so it ends up pretty messy if we have multiple concurrent imports.3 votes
We are currently evaluating how we can improve the experience and workflow around multiple pass imports. We would like to have a conversation to better understand your needs, what scenarios required multiple pass imports, and other pain points. You will have the opportunity interact with prototypes and shape the user experience for this feature. If you would like to talk with our Product Development team about this, please email: email@example.com
UX Designer | Omatic Software
The email which is sent when an import completes has the same subject line for every email "File Import Complete". This is not is helpful when scanning your emails. It would more helpful if the template name (profile processed) was contained in the subject line along with some indicator specifying whether the import processed without errors or not. For example:
Subject: IOM Lockbox Import File Completed 139 rows added/updated 0 constituents and 139 gifts.2 votes
Good call Zackary, we’ll see if we can get this in!
Promotion of non-constituents should be optional when using gift FindOmatic with Gift Barcode in batch entry.
When FindOmatic is configured to be used with gift barcode in gift batch entry, non-constituents are automatically promoted to full constituents, even when the option to never promote relationships is selected. This is especially problematic when the only match is a non-constituent and is then immediately inserted into the batch and promoted without any warning.
I understand that this is an intentional part of the design, but I believe the user should be able to control this feature. This issue has resulted in numerous records being created that should not exist.1 vote
- Don't see your idea?