Keleigh Allen
My feedback
10 results found
-
4 votes
An error occurred while saving the comment -
2 votes
-
12 votes
-
79 votes
-
3 votes
-
168 votes
-
127 votes
An error occurred while saving the comment This would be extremely useful. We have some transformations that involve multiple steps and values to evaluate. Having to update it multiple times inside of multiple formulas adds a level of opportunity for errors that is anxiety inducing. It also takes a lot of time out of my day to go through them one by one and make sure I've found them all and updated them properly.
-
3 votes
-
2 votes
-
101 votes
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).
An error occurred while saving the comment We end up with SO many duplicate phone and email entries because it is matching on type instead of the actual phone or email data. It requires constant cleanup after imports because of this. We also end up with way more email types and phone types than we actually need because its adding more numbers to the end for Email 3, Email 4, Cell phone 3, Cell phone 4, etc. I also wish I could give this more than three votes.
I have ImportOmatic processes that update Constituent Codes. If we have a record coded as Current Student and they graduate, we need to be able to either replace Current Student with Alumni OR delete Current Student and add Alumni. I will frequently end up with a file of several hundred records and the Current Student code is not going to be the same sequence number on ever record.
This lack of ability to delete or replace the constituent codes is preventing us from moving several processes into Omatic Cloud.