Omatic Cloud
131 results found
-
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 -
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 -
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 -
Update Transaction Schedule when Recurring Gift Payments are imported into RENXT batch
Gifts for payments to recurring gifts can be linked at time of import into RENXT batch. The gif shows up in the list of transactions and the amount Received is updated, but the Next transaction due: is not. This causes problems with our reminder process. The transaction schedule needs to be incremented as well.
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.
3 votes -
Add RE NXT tax declaration to list of available fields
To use Omatic for gift imports in the UK we need to be able to add tax declaration information for the donor. These fields have been added to the Sky API now, so could they also be added for mapping in Omatic Cloud?
2 votes -
Be able to match to Gift Attribute Import ID in order to update gift attributes
Seem to be able to add new gift attributes, but not update existing gift attributes. Being able to globally update existing gift attributes would be very useful
2 votes -
Update the Engaging Networks / Raiser's Edge connector to allow mapping to the Origin Source field in Engaging Networks
There is a field in Engaging Networks called Origin Source which shows what caused someone to sign up to our mailing list. I would like to be able to bring this information from EN to RE, as well as push information from RE to EN if we are uploading new records).
2 votesHi Sonia,
Thanks for your suggestion here. We are currently reviewing this idea. From our research it appears as though the Origin Source may only come from the Bulk Export API (which is what Omatic uses to pull data from Engaging Networks) on the transaction that created the constituent in Engaging Networks. I am trying to find more information about this. As a result, I want to confirm how you intend to use this field so we can be sure we are considering your use case.
Can you share when you intend to use this origin source data? Is this donation transactions or some other type of transaction that you are pulling from Engaging Networks that you hope to have this field available to use? Anything else you can share about your intent and intended use would be helpful.
Thanks again.
Steve Brewer
-
Allowing the formula to auto match based on a spouse in a record.
Example: The file I'm importing the donor name is Laura Smith but in RE NXT we have a donor of Robert Smith with spouse of Laura Smith. When these come through Omatic Cloud they are 1:1 matches but we still have to look at every single one by opening the RE record to ensure the spouse is on there. Is there a way to make the formula automatically match it if the spouse matches and the address matches?
2 votes -
matching gift pledges
Omatic Cloud needs the ability to enter matching gift pledges and matching gift pledge payments. Currently the feature is only available with Importomatic and with database view sunsetting in the near feature we need to have more functionability.
2 votes -
ability to select multiple rows when reviewing "Needs Attention" area to mass "Add" or "Delete" records
Select multiple rows when reviewing "Needs Attention" area to mass "Add" or "Delete" records. Right now we are clicking one by one, and it can be time consuming if there are many.
2 votes -
RENXT to HubSpot Export: HubSpot Additional Email Match
During an export from RENXT to HubSpot it looks like Omatic currently only looks for email matches for the email that is marked as "Primary" in HubSpot. Is it possible to consider the "Additional Emails" in HubSpot, to reduce the risk of duplicates being created?
2 votes -
Excessive number of duplicates - when donors give twice within same flat file
If a donor donates twice within the same flat file, Omatic Cloud will generate duplicate records for that donor in Raiser's Edge (because it sends records all at once). In contrast, ImportOmatic sends records one at a time, so if a new donor gives twice, it will be matched the second time.
This is especially problematic for events, when a donor will both buy a registration ticket and make a donation within the same flat file. Multiply this by the majority of the attendees for the event and it results in an excessive number of duplicates. This is a big…
2 votes -
Omatic Data Service
We currently have a subscription to Omatic Data Service with IOM to find fuzzy match duplicates during import. This service has been critical in reducing the number of duplicates created in the database. Will ODS be available in IOM+? I'm concerned that duplicate records will start to increase without it. This becomes a big issue after year-end when preparing tax receipt letters if donors have gifts spread over multiple records.
2 votes -
merge
Build an omatic cloud application for duplicate management comparable to Merge Omatic and more flexible than the RE NXT solution
2 votes -
RENXT Tags
We would like to be able to use RENXT Tags for mapping to HubSpot. This field is currently available in NXT but not available in RENXT List to HubSpot formulas.
1 vote -
Add NIN to Omatic cloud
For importing Standing Order payments from the bank the only way we can link to Constituents is by a unique ref. We currently store this in the NIN field. Could we get this field added to the omatic cloud when it is added to the SKY API (raised with Blackbaud as well). Thanks
1 vote -
Custom Fields in Every Action Connector on Contributions
It looks like custom fields are available for Contributions in the EveryAction connector, but we can't access the Contribution custom fields that are available on the Recurring Commitment formulas. Example--we're looking for a custom "Fund" field that has been created to further breakout gifts, but we are not able to map to this right now for recurring commitments. The custom field is available on the contribution.
1 vote -
Turn on the Engaging Networks QueryResult connector
Turn on the Engaging Networks QueryResult connector so we can import custom query results from EN to RE. At the moment it asks for a login email address and password when you try to use it, as well as the website URL of your EN instance. But when we try to use it with our details it says "Invalid Credentials! Authentication Failed! Username/Password is incorrect" even though we are using our correct details.
1 vote -
Send to a specific triage bucket based on a Mailchimp status field results returned during matching.
Triage currently takes specific match situations into account but I'd like to send records where Mailchimp returned "Cleaned" or "Unsubscribed" directly to the Exceptions triage bucket regardless of matching criteria. This will allow me to automate the Ready triage bucket instead of needing to review it before sending the record updates to Mailchimp. This matters because I'm trying to reduce the overall number of API transactions (Blackbaud has a threshold over which they charge me extra).
1 vote
- Don't see your idea?