Omatic Cloud
102 results found
-
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 -
Add Title as one of the fields for mapping on VolunteerHub
Add Title as one of the fields for mapping on VolunteerHub on ImportOmatic. Currently this is not one of the available fields: https://omaticsoftware.my.site.com/Support/s/article/What-Fields-are-Available-for-Mapping-from-VolunteerHub
3 votes -
FindOmatic email search
We would like to use FindOmatic to search for records using email addresses.
3 votes -
Duplicate data checks between columns
It would be helpful to have the ability to compare fields in different columns to each other, to check for duplicate values. For example, when we're working with files that contain more than one address, email, phone etc. while being able to either blank out the value if its a duplicate of another field, or keep it if it isn't.
3 votes -
Classy Transaction Type in the connector section
We need to have the Classy transaction type from the payout report in the connector.
3 votes -
Ability to send multiple values to "select multiple" contact field in Emma
We want to map our constituent codes in NXT to a corresponding "select multiple" contact field in Emma, such that all of a given constituent's codes are reflected in their Emma profile. Currently there is no way to format or transform the incoming constituent code data in NXT via Omatic such that it successfully selects multiple choices in the corresponding Emma contact field.
3 votes -
Head of Household - RENXT
We would like the ability to map to the "Head of Household" field in RENXT
3 votes -
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 votes
Emily 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! -
Improve CSV Export Format for Web Front-End Exceptions
When exceptions occur in the web front end, users can export the affected records to a CSV file. However, the exported file does not match the format used by the system's formula, preventing direct external corrections and re-import.
Currently, users must manually look up ID numbers in the original file, extract the rows, make corrections, and then re-import—adding unnecessary steps to the workflow. While small numbers of errors can be fixed directly in the web view, handling large batches this way is impractical.
Proposed Solution:
Provide the option to export the csv data so that it aligns with the format…3 votes -
Have an export profile in the LO Connector that allows for TeamRaiser registrations to be exported from RE to LO.
Omatic has gotten TeamRaiser donations to flow really well from Re to LO, but the missing piece is still the offline registrations that need to go from RE to LO. Currently we have to use Blackbaud's arcaic upload system and then still rely on RELO to pull them down into RE because the import for registrations either does not have the ability to recognize offline registrations or cannot recognize the time stamp the LO uses for offline uploads of registrations.
3 votes -
Provide the ability to overwrite an existing value with a null value in MailChimp
Currently, date fields with null values are not sent through the MC connector. I'm not sure if this also applies to other types of fields.
This means that if a date field is populated in MC, then updated to a null value in RE, the date will not be overwritten in MC with the new value.
Because we use these date fields (expiration date, date joined, etc) as segmentation criteria, this affects our marketing campaigns to targeted audiences and can cause significant problems.
3 votes -
Add connector for RENXT and Cvent
Add a connector for RE and Cvent to capture new/updated contact and consent updates and event campaign outcomes.
3 votes -
Add ability to specify the Constituent Code sequency (Primary Consituent Code) when adding or editing
Blackback RENXT considers the first or top Constituent Code on a constituent record to be the primary code. This primary constituent code is automatically used in reporting and is the default on new gift records.
We are requesting the ability to specify if a constituent code should be in the top spot when importing (creating or editing) a constituent record.
The skyapi for constituents allows a sequence to be specified when creating or editing a constituent record however Omatic Cloud has not exposed access to specify a sequence value.
The current behaviour appears to add a new constituent code to…
3 votes -
ability to use logic to pick from multiple source fields
For instance: Let's say the destination field is Last Name.
I may have multiple relevant source fields that are relevant to this destination: Legal Last Name, Preferred Last Name, etc. I may wish to map Preferred Last Name when available, but when that field is blank, use Legal Last Name.
3 votes -
Ability to Add Multiple Constituent & Gift Custom Fields in an Import Profile
Need the ability to add multiple custom fields for constituents and gifts. This would be similar to Virtual Fields in ImportOmatic, as it would be very helpful to have that same flexibility and ability of multiple attributes and additional items in Omatic Cloud so we can switch fully to Omatic Cloud.
3 votes -
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 -
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 -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 votes -
Name fields from Stripe to populated
Stripe specific parsing reques
3 votes -
Ability to map to Mailing ID and Finder Number on gift record
These fields aren't available through the Blackbaud API, but we have numerous queries and reports that rely on them, dating back to when we first started using RE. We use the Mailing ID field to track the platform through which a gift was made, and the Finder Number field to identify constituents from acquisition mailing finder files. If we can't map to these fields in Omatic Cloud, it will require significant changes to our existing workflows. Currently, I'm adding this data to gift records with a Blackbaud import after importing through IOM+, which is not an efficient process.
3 votes
- Don't see your idea?