Jessica Daggett
My feedback
21 results found
-
28 votesJessica Daggett
supported this idea
·
-
6 votesJessica Daggett
supported this idea
·
-
8 votesJessica Daggett
supported this idea
·
-
8 votes
An error occurred while saving the comment Jessica Daggett
supported this idea
·
-
4 votesJessica Daggett
supported this idea
·
-
2 votesJessica Daggett
supported this idea
·
-
15 votesJessica Daggett
supported this idea
·
-
20 votesJessica Daggett
supported this idea
·
-
1 voteJessica Daggett
shared this idea
·
-
162 votesJessica Daggett
supported this idea
·
-
31 votes
An error occurred while saving the comment Jessica Daggett
commented
Any updates to this feature since May/June?
An error occurred while saving the comment Jessica Daggett
commented
Fantastic, this will allow me to use Omatic Cloud for flat file imports once this is released! I don't know if it's possible to also have it add "Unit" or "#" or something in front of a lone number or letter at the end? For example people will type in "1451 24th Street 528" and would be great to end up with "1451 24th St #528". Not sure if that's possible. It would also be amazing for the transformation to work well with concatenate for a second line. For example, if people enter "4300 Cherry Creek Drive South" on one field and "Apartment B" on a second field, for the transformation/concat to allow us to import "4300 Cherry Creek Dr S Apt B" all into Address Line 1. Thank you for your consideration!
-
1 voteJessica Daggett
shared this idea
·
-
6 votesJessica Daggett
supported this idea
·
-
17 votesJessica Daggett
supported this idea
·
-
74 votesJessica Daggett
supported this idea
·
-
19 votesJessica Daggett
supported this idea
·
-
76 votesJessica Daggett
supported this idea
·
-
39 votes
An error occurred while saving the comment Jessica Daggett
commented
The reason this is so critical for us is the address and RegEx transformation dictionary that we have in IOM. It has hundreds of entries to help format addresses properly (abbreviations, no punctuation, etc). I now have to try to build those in the Cloud and not only that, I have to build them over and over for all our Formulas!! So maybe converting existing dictionaries isn't possible, but finding a way to create this one in the Cloud is what we need. It would be ideal if you had a built-in transformation to do this to addresses as I'm pretty sure most clients want to adhere to USPS standards.
Jessica Daggett
supported this idea
·
-
71 votesJessica Daggett
supported this idea
·
-
5 votesJessica Daggett
supported this idea
·
YESSSSSS! I LOVE this feature in IOM! It is so easy to review multiple potential matches all at one time, in one quick screen, and see all the key biographic data that might make someone the correct match. You even sort them by match liklihood! The amount of clicking into multiple or 1:1 matches and then having almost no data to compare which one is the correct match is currently a really poor roll-out in Omatic Cloud. Why lose the great functionality you built into IOM?? There should be a standard repository of common fields that we can match on (WITH ability to determine the length - i.e. first 2 characters in first name, first 8 characters of address), even when those fields are not contained in the import file mapping for that particular formula. Could you just please replicate what you have in IOM so that we don't lose functionality by "upgrading" to the Cloud?