ImportOmatic

Welcome to our official ImportOmatic feedback forum. Do you have an idea? Do you recognize a good idea when you see one? We want to hear from you!

ImportOmatic should...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Add the ability to pause an import

    It would be nice to be able to pause an import, head into mail, query, etc, and then resume importing at a later time!

    267 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow choosing of email/phone type when matching records

    I know that we can set it to create a new type (email 2, etc) but ideally I would like to be able to choose every time which type the new phone/email will go under. The major reason for this is Spouse Email. If we import a transaction from a spouse with their name and email the spouse is matched correctly, but their email is set as the new default email for the whole record instead of being put in "spouse email".

    Basically we want to be able to treat emails matched by spouse records differently than ones matched to…

    156 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Match on the actual phone number (not just type) when importing phone numbers

    We would like the ability to match on the actual phone number or email (not just phone type) when importing phone numbers. We have a file of wrong phone numbers from our phonathon vendor. I would prefer to update these numbers through IOM instead of manually updating the records one by one.

    146 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →

    Hi, Omatic here! After reviewing this request, we think we may have misunderstood Joan’s initial request when we responded quite awhile back. We’ve corrected the suggestion’s status, but we also included the initial response below for context. Please feel free to continue to vote on the idea and add your comments!

    Previous response – Hi Joan, IOM already matches on any email address. We already have phone number matching scheduled for the next big release, but you can have it now simply by mapping your phone numbers as email addresses in your Import-O-Matic profile (RE treats phones and emails pretty much the same).

  4. Allow easy removal of duplicate addresses on the fly

    Per this article in the user forums, it would be helpful to be able to clean up duplicate addresses automatically or easily while running through address processing during import.

    http://www.omaticsoftware.com/Forums/tabid/108/aft/1308/Default.aspx#3144

    127 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Move old phone number to next sequantial number

    Currently I can bring in a phone number to the next available # if that #1 is alreday taken. However, I want to bring in the new phone number as #1 and move the existing #1 to number 2, etc. The only option I have now is to move it to an attribute. So now I have to query on those attributes and move them to the next available slot.

    127 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. Update dictionary table entries

    Ability to update the dictionaries with newly added table entries. Currently the dictionaries do not automatically update the table entries.

    85 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  7. 84 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Import comments for Major/Minor fields

    Please add the ability to import Major Comments to education relationships.

    82 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    10 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. create "If...then...else" enabled fields to choose between values from different fields

    I would love to make use of this feature, especially, if one field is not blank, use that value, but otherwise use the value of a different field. Just like a Word merge! How hard could it be?! LOL! Come on, Omatic, you could do it!

    79 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. 70 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    5 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. 69 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  12. allow for the importing of soft credits. Currently IOM does not allow soft credits to be imported on their own.

    We have a need to apply soft credit to a spouse when the other spouse has made a gift. At some point when 2 constituents are found to be related, we need to apply the soft credit to the other spouse. We use SQL to create an import file to apply the missing soft credits via R/E import. We would like to perform this same function using IOM.

    55 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Email and Phone fields in Duplicate Criteria sets

    Please include Phone Number and Email address fields in Individual Duplicate Criteria set building. I.e. It should be possible to have [FirstName, LastName, Email] or [FirstName, LastName, Phone/Mobile] as a criteria set.

    Some of the data files we receive only have 3 fields: first name, last name and a phone number or email address. In the absence of an actual phone/email field in the criteria set, the search tool becomes overzealous and returns every possible match for first name and last name only - this list can be very long, the matches are very crude & irrelevant making the import…

    47 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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:

    1. "Employee" check box is unchecked

    2. Relationship and Reciprocal changed to "Former Employer" and "Former
    Employee"

    46 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Allow for more thorough checking of previous education records.

    We get education records from our school that sometimes are duplicates of old records. This may be because a alumnus goes back for one class, or for any other reason. It would be great if IOM would check for duplicate educational records like it checks for addresses. Based on what it can check for now, I don't quite get the amount of control I would like to have to make sure everything is working properly.

    If it were like the address match feature, that would be fantastic! Thank you.

    43 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add gift attributes to existing gifts

    Allow an IOM profile to add gift attributes to existing gifts.

    41 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Apply defaults on spouse promotion

    When a non-constituent spouse is promoted to constituent record the default settings for new constituent are not applied. In our case that means no default constituent code, salutation, addressee, or nickname. There should be a checkbox with the spouse promotion option to apply a default set.

    40 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Move Virtual Fields up or down

    Allow users to move the Virtual Fields up or down in the view. This way as they make updates to the file, they can move all fields that may need to be updated for each run to a certain part of the list instead of having to search line by line.

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Match financial institutions more intelligently

    Today Sharifa and I spent hours battling against some fairly opaque error messages. In the end it turned out that adding a "branch name" for both the gift and the relationship was enough to push it through, but this has meant that our financial institution table is now polluted by some branch names that are just "branch" - clearly not ideal.

    I think this must be because our financial institution table was already quite messy. When I look at the records that caused exceptions, it appears that they were all trying to use banks which either had a branch name…

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Ability to control which users can see specific import profiles

    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.

    34 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →

    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

← Previous 1 3 4 5 14 15
  • Don't see your idea?

ImportOmatic

Feedback and Knowledge Base