Omatic Cloud
333 results found
-
Ability to import gift note
Currently I cannot import a flat file of gifts into an NXT/webview batch because I want to add a gift note.
1 vote -
Include/change the automation for spousal soft credits from the gifts field mapping to a relationship field mapping
In Omatic Cloud I came across the spouse soft credit under the gifts field mapping and believe this should be changed to the relaionship field mapping. When I add my new parents/grandparents, I would like to mark their spouses as automatically receiving soft credit prior to their first gift being received. That way when I add the gift in the Raisers Edge after my import has successfully been uploaded, I will not have to remember to manually add the sodt credit, it will automatically default to the spouse record.
1 vote -
Enforce the Organization Relationship Address to default on the Constituent Address Field for Businesses
I had an issue recently in Omatic Cloud where I could not add business address information to the organizational relationship record so that it defaults as a business address option on the constituent address. Instead I needed to include both the the organizational relationship to show the Company Name and Position (without an associated address, this was a blank/empty field), as well as, adding a second constituent address separately and labeling it as business address. I now have to manually go into Raisers Edge and copy each constituent business address and paste to each of the businesses on the relationship…
1 vote -
Calculate ignore text or have transformations within calculation - specifically remove text (ex. $)
Transformations within calculation - specifically remove text (ex. $)
or have the calculation ignore text such as "$" and only respect/ingest numbers since it cannot calculate at all if there are any non-numeric characters1 vote -
Need Calculate Transformation in Concatenate
We need the ability to use the Calculate transformation inside the Concatenate transformation like the other transformations. We see this use case with fees, events, etc that have multiple amounts available that need to have the calculate transformation applied to subtract fees or multiply by the quantity of tickets and there are conditions where we would take one value over the other. You can only do this with a concat right now.
1 vote -
Inactive Existing Emails
We need to be able to mark over 800 EXISTING emails inactive in the RE database. These are emails that bounced back as invalid from an email blast we sent out. It will take too long to manually mark these in each person's record. This would be very beneficial if we were able to do this through Omatic.
1 vote -
Add Google Drive/Sheets Connector
We are a Google Workspace customer. We often get event registrations and other data that goes from a form to a Google Sheet. It would be fabulous to be able to use a Google Sheet as a data source to import data to Raiser's Edge without having to download it to Excel, recheck and fix the formatting since Excel always messes with field formatting and leading zeros, then upload the Excel file to Omatic Cloud.
3 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 -
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…
-
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.
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 -
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 -
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 -
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.
2 votes -
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
- Don't see your idea?