Omatic Cloud
138 results found
-
Adding opportunity_ID to link actions to opportunities (proposals)
In reviewing the SKY API documentation on importing Actions into RENXT, there is a field called “opportunity_id” that would allow us to link actions and opportunities/proposals. That field is not available when mapping an Omatic Formula. That would be huge.
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 -
email notification
Have specified Omatic Cloud users receive notifications when there are gifts pending in the "Needs Attention" queue.
4 votes -
Enforce imported Name Format order on new constituents in RE NXT
Allow us to set the order that Name Formats are imported into new constituents. Those of us with a standard ordering for addressees and salutations need this. Currently, RE NXT just decides on an order, which makes them hard to review.
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 -
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 -
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 -
Name fields from Stripe to populated
Stripe specific parsing reques
3 votes -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 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 -
Make popular / favourited translations available with one click
In Importomatic, to add Proper Casing takes one click. In Omatic Cloud it takes around 7. It would be useful if we could "favourite" certain translations, so that these are able to be applied with a single click.
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 -
FindOmatic email search
We would like to use FindOmatic to search for records using email addresses.
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 -
MailChimp SMS into RENXT
Have MailChimp SMS data recorded in RENXT using the connector in the same way the Email data is.
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 -
Map multiple fields to NXT
Make the ability to map multiple fields from Mailchimp to a note in an action in NXT.
3 votes -
Add Sent Email API for Engaging Networks
Engaging Networks offers a paid API service in addition to their Bulk API that is the only way to extract specific email send information, regardless of a user's interaction with that email. We need to be able to import email activity into Raiser's Edge, including what email a constituent was sent so we can report on appeal response, but can only do so with the Sent Email API.
3 votes -
Export from RENXT to flat file
I would like to have an automated export in Omatic Cloud from RENXT to a flat file. This will help automate data to other systems in our organization.
3 votes -
Add Org Relationships Second Time
When importing organizational relationships, the organization relationship may exist already with an end date. We would like to add an additional org relationship with a current start date. Currently, it is matching to the existing organizational relationship and erroring out because "start date cannot be before end date".
Therefore, we must manually add the relationship if the relationship already exists. Example, we want to upload a new employee to our database but they were a former employee 20 years ago and that org relationship is recorded as a former org relationship on their record to our university. Therefore, I cannot…
3 votes
- Don't see your idea?