Omatic Cloud
369 results found
-
Log when a formula is reprocessed in Activity History
Currently the activity history does not show when a formula is reprocessed. This info would be helpful especially when working through the exceptions buckets. it would all use to better track errors that are recurring.
4 votes -
Enforce Default Data Differences Selection During Setup
It would be great to make the "Default Data Differences" selection more transparent to the user during setup. It opens them up to the risk of overwriting data in mass if they are sending records from the "Ready" bucket and have left the default difference as Source and have not switched it to Destination.
4 votes -
Constant Contact Preference Updates
It does not look like there is currently a way to reflect preference/interest updates from CC. You can see who is on a list, but there is no way to see if a contact has been removed or not on a list in CC.
4 votes -
Don't Update Existing Blank Values in Destination when Default Data Difference is Destination
When setting the Default Data Difference to Destination, we'd like to leave an existing destination value that is blank. We would not want to import incoming values in this scenario.
This is happening specifically when a record lands in New, but we know there's a match so we use Override to match to the existing record.4 votes -
Enable File-to-File Transformation & Export in Omatic Cloud
Currently, Omatic Cloud only allows transformations when importing data into Raiser’s Edge or other connected systems. However, it would be extremely beneficial to have a file-to-file processing option. This would allow users to:
Upload a spreadsheet, apply transformations, and export the transformed data as a new file (CSV, Excel, etc.).
Use Omatic’s powerful transformation tools without requiring integration with an external database.
Improve data cleaning and preparation workflows for reporting, imports, and other external processes.
This feature would save time and expand Omatic Cloud’s usability beyond direct imports. Please consider adding this functionality in a future update!4 votes -
Ability to tag and filter formulas in Omatic Cloud
Ability to tag and filter formulas in Omatic Cloud. I have over 60 different formulas and most vary from the same set of rules i.e. we have two formulas for one file so we can adjust fields for new and existing records. Right now the tabs are useful but since they are user specific when I sign up a new user I have to spend time helping them find the right formulas. If there were tags I could assign departments, new vs existing, and formula type to make the search easier. It would also be nice to be able to…
4 votes -
Matching on middle names and birthdates
We have 70,000 individuals in out database, so we get a lot of people who match on common first and last names. Being able to use middle names or birthdays would be a huge help in distinguishing who's who.
4 votes -
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 -
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 -
Enforce Unique Formula Names
Formula names should be unique in Omatic Cloud. Multiple formulas with the same name can cause confusion during processing or reporting an issue with support.
4 votes -
Organization Information in "Verify your account" email
When adding a user to an account, it would be helpful to see the Org Name and potentially the tenant name associated with the email verification. The current email does not include any identifying information and makes confirming access challenging. It would be much easier for users to be able to directly click on the OC URL from the "Verify your email/account" email that is sent out when a user is given access to an OC instance.
4 votes -
Separate formula Type for HubSpot Email Subscriptions
Currently, the HubSpot formula "Contacts" handles all subscription information. Could this information to be handled separately in a stand alone formula since the "Contacts" formula handles all changes, not just email subscription changes.
The current process is noisy and creates a high volume of records that are unrelated to email subscription changes. This is also problematic for the HubSpot connector given API hits.
4 votesWe are planning to add this feature in Q4 2023!
-
Add Relationship Attributes
We would like the ability to send relationship attributes through Omatic Cloud to RENXT.
3 votes
Emily Dalton
responded
Hi Anna, In RENXT, if you add an attribute to a relationship, it requires that relationship to be a full constituent. This is a bit different than how relationship attributes functioned in RE7. By mapping relationship attributes through RENXT, would you be okay with those records automatically being promoted to full constituents? Best, Kristen -
Add ability to export membership data out of RENXT
We were hoping to be able to push data into Raiser's Edge NXT surrounding membership. We would need:
Membership Category
Date Joined
Date Expires3 votesEmily Dalton
responded
Currently these fields are not available in Blackbaud's SKY API. However"," once they are available"," we will look into adding this information! -
Head of Household - RENXT
We would like the ability to map to the "Head of Household" field in RENXT
3 votes -
Delete Field Value Using Dedicated Syntax
We often have the need to delete/clear a field when importing. It would be great to have a dedicated syntax that we can map to indicate that the mapped field should be replaced with null.
E.g. if we map {DELETE} it would remove the value in the field in Salesforce that we are updating, leaving it blank.
This would allow blank fields to be ignored, whilst giving users a way to very intentionally delete a fields.
Two examples:
1) We have a file of donor data where invalid/incorrect email addresses and phone numbers have been flagged. We can therefore import…
3 votes -
Search Functionality in 1:1, 1:Many, New Record Queues
It would be helpful to search function across all the record queues to find certain points of data. This could operate similar to a Ctrl F but across all pages within that bucket.
3 votes -
Allow multiple bank accounts to be selected for template
We have 120+ Affiliates/bank accounts. When we cut checks, we will do it for 25-50 different ones on 1 day. Being able to select multiple Affiliates/banks would save us so much time instead of entering 1 at a time and then getting a template to upload at our bank. 1 upload for 25+ affiliates would be great! (Upload our information and then the screen would have boxes to 'check mark' and empty boxes to fill in the check # range.
3 votesThank you Missy for the idea. This is definitely an interesting use case. I am assuming that the Bank is the same for all 25 affiliates, and the only difference is the account in FE. And you would expect 1 file to be generated that has checks for all of your affiliates that are uploaded to your bank via that 1 file. Can you confirm my understanding?
For the update I would think we would need to make available all of the settings for each account you choose from FE such as starting/ending check number, include voids, and any other settings that is required for the bank format.
-
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 -
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
- Don't see your idea?