Omatic Cloud
104 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 -
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…
1 vote -
Advanced Name Processing for Omatic Cloud
Currently there is only a way to have exact matches on records. It would be helpful to have an Advanced Name matching option in Omatic Cloud, which is similar to the IOM option to score likelihood that a similar record exists in the system.
When a similar record is found, the records could go to Needs Attention for review, with an option to create New or Match.
The example of this is if a last name has an extra space or with multiple last names with a hyphen separating them.
It is faster for me to review Needs Attention records,…
31 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 -
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 -
Integrations/Formulas | Mapping | Total Sum of Two Cells/Columns from an Import File
Built-in feature that allows combining two column headings to create a total sum during the mapping process.
Example: scenarios of summing platform fees and transaction fees.
1 vote -
Deceased indicator
Display a deceased indicator in the data differences columns of the triage buckets, similar to displaying Mailchimp contact status. This will help with decisions without me needing to step into the record just to find out they're deceased.
1 vote -
Enable Importing Event Registrations from GiveCampus
The GiveCampus integration currently supports only importing gifts. Events is another large use for the platform and one we're looking to leverage. Being able to utilize this would improve our process flows greatly.
8 votes -
Ability to map Action Notepad Type
When importing CC data into NXT via Omatic, the default for Action Notepad Type is "Added via Web View". This default is not effective in allowing us to report to our Board and stakeholders outcomes. After uploading actions we will have to manually change this field.Having the option to define or map this field will give us richer data and better metrics to report on.
5 votes -
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.
1 vote -
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 -
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 -
List Management available
Given the plan for RE to move to a "total web solution" which will ultimately replace database view, for users of IOM List Management, could this feature be made available through Omatic Cloud?
7 votes -
Record match search
It would be helpful to also have the option to include a LinkedIn url address as an option for constituent match search for imports.
1 vote -
FindOmatic email search
We would like to use FindOmatic to search for records using email addresses.
3 votes -
allow to import non-constituent participant records
We would like to be able to load non-constituents into events as participants via the cloud integration.
10 votes -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 votes -
Abilitly to do relationship matching in RE NXT based on Constituent Import ID
Currently, when importing relationships to existing constituents in RE NXT, the only option for matching to existing constituents is to map to either 'Constituent Lookup ID' or System Record ID. We really need to be able to map to Constituent Import ID. Especially when using a hybrid approach using both IOM-Classic and IOM+/OC, IOM-Classic furnishes the Import ID as an output field, but not the 'lookup ID' nor the System Record ID. This would be a very useful and valuable feature, and would allow clients to leverage the benefits of both versions of IOM.
10 votes -
Abililty to map Constituent Import ID when importing soft credits in RE NXT
Currently, when importing gifts with soft credits in RE NXT, the only option for matching to existing constituents is to map to 'Constituent Lookup ID'. We really need to be able to map to Constituent Import ID. Especially when using a hybrid approach using both IOM-Classic and IOM+/OC, IOM-Classic furnishes the Import ID as an output field, but not the 'lookup ID'. This would be a very useful and valuable feature, and would allow clients to leverage the benefits of both versions of IOM.
7 votes -
Email notification when formula completes or times-out
Have an option to enter an email address (or two) to notify when a formula completes or when the formula times out.
34 votes
- Don't see your idea?