Omatic Cloud
326 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.
15 votes -
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 -
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.
1 voteHi 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…
-
Add Custom Fields to the Fundraise Up Connector
Custom fields in Fundraise Up hold very important information that allows us to easily integrate this data into Raiser's Edge NXT. Before the connector we were able to pull this information in via the flat file and not having these fields makes it difficult to get our full set of gift data when we import.
6 votes -
Ability to Change an Email/Phone Type based on and Email/Phone Number Match
We often get a spreadsheet of Emails and/or Phone Numbers that have been discovered to be no good. It would be nice to run these through Omatic and if they match a Phone or Email Number on the record change that Email/Phone Type Category. Example: test12@msn.com has been discovered to be a bad email address. Run it through Omatic and any Email that is test12@msn.com change the email type from Home E-mail Type to Previous E-mail Type. Or even go a step further and only change the Email Type if it is a specific Email or Phone Type. I this…
6 votes -
Omatic user name populated as record owner
Populate the Omatic user name who is uploading the records to Salesforce into the associated records (opportunity, contact(s), and accounts.
3 votes -
Ability to Filter Out Test Emails for Salesforce Marketing Cloud
We are pushing Salesforce Marketing Cloud email data into Raiser's Edge actions through Omatic. We want the ability to test emails for any constituent in Salesforce Marketing Cloud, but not have those emails show on the constituent record they were tested for in Raiser's Edge. They didn't actually receive the email. There is not currently a way to filter out test emails. We learned the test email will have its own JobID and show an email in the TestEmailAddr field.
1 vote -
Ability to Filter Out Test Emails from Salesforce Marketing Cloud
We are pushing Salesforce Marketing Cloud email data into Raiser's Edge actions through Omatic. We want the ability to test emails for any constituent in Salesforce Marketing Cloud, but not have those emails show on the constituent record they were tested for in Raiser's Edge. They didn't actually receive the email. There is not currently a way to filter out test emails. We learned the test email will have its own JobID and show an email in the TestEmailAddr field.
1 vote -
RENXT <> HubSpot list mapping
We would love to have year to date giving included in the RENXT <> HubSpot list mapping. I see greatest gift, gift gift and latest gift, but having YTD giving would be super helpful for donors who give multiple times a year.
1 vote -
Transformations: Completely delete/remove data field
I would like to see that one of the transformations have the ability to completely delete/remove that field. One of the examples that I have come across is for consistuency codes. We use them if someone is giving at a certain amount annually. But if they are not at that level anymore, we need to delete the code. But I can see this being used for attributes or duplicate pieces of contact information.
1 vote -
Selecting Mailchimp Journeys for Import
We use Mailchimp's Automation Journeys for our emails, we can't see these to select from in the Mailchimp to RE NXT connector. We would like to apply an assigned appeal to these records in RE NXT who have started on a Journey, in that way they are excluded from being selected to import to mailchimp again and tell us who has had comms.
4 votes -
Need override in all grids
Whether a Match was found or not, we still may need to use override as an option.
Examples are employees who use their cc for transaction yet we know it is meant to be for their employer, and not necessarily the cardholder. This particularly becomes more important for events, as the end donor and their employer are in our CRM separately.2nd Part is when choosing a record to use for Override, the selected record should reflect some information to insure we chose the correct record. Currently if we omit a first and last name because we are entering a…
3 votes -
Create static query option using Omatic cloud or connector imports like in Classic imports.
BB RENXT now has query and we should have the means to create a static query when we use Omatic Cloud or the connector just like in Database view and omatic classic. It's a nice log of all data imports and it can be used to reverse or for an end user to check that their import afterwards.
2 votes -
OC Transformations in Alphabetical Order
Transformations are not currently in alphabetical order but it would be helpful to reorder those so they are in alphabetical order.
1 vote -
LO Groups to Mobile Commons
It would be helpful to have a LO Groups to Mobile Commons formula. Currently, there is no filtering available when ingesting data from LO.
1 vote -
Participant guests in Classy
Would like to see the ability to import guests associated with a participant in Classy to RE NXT event record.
6 votes -
Security
In RE we have very granular security. It would be great if Omatic could link to RE security roles? That way you can accurately see who ran the import/changed the records (last updates by in RE) instead of who connected omatic to RE environment.
** Or a little more granularity within the Omatic user settings would be great! Example the option for data processors to not have the ‘add’ or ‘send’ button, only match/override(link)/delete and move to ready would be very helpful, so that someone with higher security can review & send.3 votes -
Ability to delete Custom fields
It would be helpful to have the ability to remove Custom Field Attributes in NXT, not just add them.
1 vote -
Ability to Filter on Refunded Gifts in EveryAction
Currently, our EveryAction API ingests on modified date and that brings in refunded gifts. Those refunded gifts do not have any indication that they are refunded and resemble true gifts. Request is for some filter on refunded gift or the inclusion of Refund/Adjustment information fields.
1 vote -
Ability to Access Emma Sent Email Date
It would be helpful to have the Emma "sent date" for the Email Campaign Activity formula type. We can technically access this through including the "sent" activity in the filtering, however, that adds high record volume that is uncessary and could cause ingestion/processing issues down the line.
1 vote
- Don't see your idea?