Omatic Cloud
365 results found
-
Fuzzy Organization Name Matching
Currently, Omatic Cloud does not support fuzzy name matching for organizations. Organizations can only be matched on name exactly. In this case, if you were to try and import employment data, minor variations in organization name will force you to manually match with existing organizations or you will end up with multiple duplicate organizations within your database. Fuzzy organisation name matching would make this process much simpler and streamlined.
18 votes -
Allow defined type property for the column
The table, when it doesn't explicitly know the data type of a column, defaults to sorting its values as strings. This causes numbers to sort incorrectly (e.g., '10' appears before '2'). For proper numerical or date sorting, the table requires either a defined
typeproperty for the column (e.g.,type: 'number') or a customsortfunction that understands how to compare the specific data type.3 votes -
Allowing the formula to auto match based on a spouse in a record.
Example: The file I'm importing the donor name is Laura Smith but in RE NXT we have a donor of Robert Smith with spouse of Laura Smith. When these come through Omatic Cloud they are 1:1 matches but we still have to look at every single one by opening the RE record to ensure the spouse is on there. Is there a way to make the formula automatically match it if the spouse matches and the address matches?
2 votes -
Increase number of search scenarios
Increase number of allowed search scenarios until Match Settings / Contact Match Search to more than five. Our use case is to match on ID (primary), then Name, Personal Email, Work Email, Alt Email, and Mailing Address.
2 votesHi Hannah - Thanks for your idea. One thing you may not be aware of is that with Salesforce if your object has more than 1 email address field then you can choose each of those email address fields when you create an Email or Name and Email match scenario. Thus instead of creating a match scenario for each of your email address fields in Salesforce you can create one match scenario and choose all of your email fields in that single match scenario. There is an implied OR between each of the email addresses when performing the search.
For example, suppose I have 3 email address fields (per your description) in Salesforce: Work Email, Personal Email and Alt Email. Suppose my incoming email address is steve@myorgname.org. I then add an Email match scenario and choose each of those email address fields in my match scenario. When Omatic Cloud attempts to match on email address the query…
-
Review menu scrollbar
On the review menu it is a mild inconvenience to have the scrollbar all the way at the bottom, would be awesome to have it available at the top or at any moment in the review screen to see the fields
2 votes -
Add new GoFundMe Pro Channel to connector
GoFundMe Pro has added a new Channel feature for the Peer 2 Peer campaigns. We'd like this added to the GFMP connector for importing transactions.
1 vote -
tabs
More Tabs! I'm ok with having an "All Formulas" tab, however I like to have one tab per vendor, and I can't do that now.
2 votes -
1 vote
-
other name format for tributes
when creating tributes we need an "Other Name Format" to add to the record. This is available for consittuents, but not for tribute records.
3 votes -
US phone number - catch incomplete phone numbers
Add this as built in code in the telephone formatting options so there are built in options to catch "bad" data, in this case incomplete phone numbers
US Phone Number Normalization
Goal: normalize to digits, then detect “short” values and exclude them.Steps on the phone field
Telephone format (or use Replace to strip punctuation)
Normalize the phone first so only digits remain (remove spaces, dashes, parentheses, etc.). If you don’t use Telephone format, add Replace rules to remove “(”, “)”, “-”, “ ”, “+”, “.”, and “x/ext”.
Fixed Length Formatting
Fixed Length: 10
Append Value: choose a unique character,…1 vote -
option to not overwrite receipt type
we have to map to receipt type as this is a required field when creating constituent records. But this means the receipt type is constantly being overwritten, which we don't want. Can we have options, similar to what is available for email/phone number, where we can choose to not overwrite it if a match is found
3 votes -
Ability to copy detail rows
Need the ability to copy detail rows in as well as pre-processing rows. Very often, most configurations in multiple rows are the same, with the exception of only a few things (or sometimes just one thing) that needs to be changed. The ability to copy a detail row or a pre-processing row, and then change one or two configuration items, would save a great amount of time in configuring complex formulas.
2 votes -
test connection
Particularly while I am setting up or testing a new connection I find myself going in to edit the formula often. Each time I go in I have to wait for the connection to be tested. I think it would save a good bit of time if the connection testing was separated out so that you could make changes a little at a time. If you have just setup a connection and its tested, that's not likely to change within the first day of being setup.
1 vote -
Add ability to import perpetual recurring donations from Encompass
Perpetual recurring donations is a separate endpoint in Encompass. We would like to be able to import these transactions.
13 votes -
email notification
Have specified Omatic Cloud users receive notifications when there are gifts pending in the "Needs Attention" queue.
1 vote -
Allow phone match as a search scenario
Currently, OC does not have phone number available as a search scenario even when phone is mapped within a formula. This is essential to have because we otherwise wind up with unnecessary duplicates that could have been prevented.
24 votes -
Add Classy Live Transaction Types
Classy Live has different transaction types available than Classy. Not having the Classy Live transaction types available is creating a lot of manual work on our end because we use these types in a transformation for the package code in Raiser's Edge.
3 votes -
Allow Custom Routing-Omit to compare Source Fields to Destination Fields.
Use Case: RE-Nxt to Salesforce (for Email)
We are integrating RE Constituents to Salesforce to utilize Account Engagement to send our emails. As such, we are only sending down a few fields { Cons-ID, First, Middle, Last, Email..}. The formula is based upon Constituent-Date-Changed in RE. There's lots of things on a Constituent record that get "touched" each day that triggers a change to the Constituent-Date-Changed field, despite there be no effective change to the fields in our formula.
Even after getting a Primary Match across Constituent-ID, we would like to implement a Custom Routing to Omit if *all of…
1 vote -
Formula Exceptions Automate Reprocessing/Retrying
Almost always when Formula Exceptions pop-up (as opposed to Destination Exceptions), they are timeout or connection issues and customers have to click into that bucket and then just click the Reprocess button. This could be automated to retry a certain amount of times on failure or after a time period and would save customers an annoyance. (Customer papercut type improvement)
1 vote -
Export returned data in the queue
Making use of Omatic's great finding and filtering functions I attempted to export a queue and to my surprise, there was no "RE ID" in the export, after talking to lovely tech support agent, Amanda, she suggested I add this idea here.
Exporting the returned data, specifically the "matched" RE ID, given in the queue would allow me to quickly filter, cleanup and manipulate the .csv file in Excel. This would be tremendously useful for me, as I could notify the Team before the gifts are processed, not to mention the added benefit of making edits prior to sending to…
3 votes
- Don't see your idea?