Omatic Cloud
113 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 -
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 -
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 -
Allow mapping to gift subtype and gift code for pledges
Allow mapping to gift subtype and gift code for pledges. I currently get a message that this in unavailable for pledges.
4 votes -
Allow for the Import of Gift Aid Declarations in Omatic Cloud
Absolutely critical for clients in the UK doing any gift importing. This is a feature that is UK specific but needed to move IOM profiles to OC.
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 -
Be able to export CQS transactions from RE to EN via the connector
Opt-in questions with the type “Opt-in Confirmation” (CQS transactions) are not available to be exported to from RE to EN using the connector. Only QCB opt-in transactions appear.
Engaging Networks have implied that this link should help . https://speca.io/engagingnetworks/engaging-network-services?key=726cda99f0551ef286486bb847f5fb5d#add-or-update-supporter . The name in the REST API is Double Opt-in. The type is CONF
4 votes -
Exclude Administrators
Currently, LO connector imports administrators to Raiser's Edge. However, you can't update Luminate Administrators with LO connector, which is good.
The profile should ONLY work with constituents, NOT user accounts. Filtering out administrators should be an option without a group filter from the profile settings.
3 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 -
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 -
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! -
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 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 -
Name fields from Stripe to populated
Stripe specific parsing reques
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 -
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 -
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 -
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 -
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
- Don't see your idea?