Omatic Cloud
347 results found
-
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.
1 vote -
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 -
Fuzzy Organization Name Matching
Currently, Omatic Cloud does not support fuzzy name matching for organizations. Organizations can only be matched on name exactly. In this case, if you were to try and import employment data, minor variations in organization name will force you to manually match with existing organizations or you will end up with multiple duplicate organizations within your database. Fuzzy organisation name matching would make this process much simpler and streamlined.
15 votes -
Add ability to import perpetual recurring donations from Encompass
Perpetual recurring donations is a separate endpoint in Encompass. We would like to be able to import these transactions.
13 votes -
Increase number of search scenarios
Increase number of allowed search scenarios until Match Settings / Contact Match Search to more than five. Our use case is to match on ID (primary), then Name, Personal Email, Work Email, Alt Email, and Mailing Address.
1 voteHi Hannah - Thanks for your idea. One thing you may not be aware of is that with Salesforce if your object has more than 1 email address field then you can choose each of those email address fields when you create an Email or Name and Email match scenario. Thus instead of creating a match scenario for each of your email address fields in Salesforce you can create one match scenario and choose all of your email fields in that single match scenario. There is an implied OR between each of the email addresses when performing the search.
For example, suppose I have 3 email address fields (per your description) in Salesforce: Work Email, Personal Email and Alt Email. Suppose my incoming email address is steve@myorgname.org. I then add an Email match scenario and choose each of those email address fields in my match scenario. When Omatic Cloud attempts to match on email address the query…
-
EveryAction Field - "Campaign Type"
It would be helpful to have "Campaign Type" as an endpoint for EveryAction. This field would allow for the tracking of donations through various campaign types.
1 vote -
Ability to import contact record for Organization Gifts in EveryAction
Currently, we don't have the ability to import the primary contact/relationship for an Organization gift with the EveryAction connector. Adding this functionality would allow for more complete gift records as that is critical information missing.
0 votes -
Custom Routing - Activity History
Would be beneficial to see in the activity history when records are deleted/removed due to the custom routing settings. This way if we see x number of records ingested but only see x number in the buckets it can help us audit the numbers we are seeing. Right now records just 'disappear' depending on the settings.
3 votes -
Facebook Fundraiser ID Field Available for Omatic Cloud
It would be great to be able to make the Facebook Fundraiser ID in Luminate Online (TeamRaiser) available within Omatic Cloud so the value can be synced with other environments, like Salesforce. As fundraising options/tools/vehicles continue to grow, we'd like to be able to report within our database of record, who is using Facebook as a fundraising tool and who is not. It does appear that Blackbaud makes this field available within it's API.
https://kb.blackbaud.com/knowledgebase/articles/Article/199607
https://developer.blackbaud.com/lo-api/loapi/teamraiser/createAndLinkFacebookFundraiser
https://developer.blackbaud.com/lo-api/loapi/teamraiser/updateRegistrationThank you!
1 vote -
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.
1 vote -
Autocorrect empty fields instead of needing "Is Not Blank" Replacement
It would be great if the system can autocorrect for the error were we are creating a field type/category with blank data coming through for some individuals instead of needing to remember to enter the Replace transformation or go back and enter it post error message. Small papercut that could make a big User Experience difference.
1 vote -
Add Prospect Status
From what I can tell Prospect Status is not a field we can currently load to.
1 vote -
Enable Importing of Pledges from GiveCampus
The ability to import Pledge Commitments and Pledge Payments through the GiveCampus connector API would be incredibly valuable. Currently these types of gifts can only be processed from a flat file, and this would be an incredibly useful addition to the connector functionality overall.
3 votes -
Upgrade EveryAction connector to post gifts to EA.
The EveryAction connector only allows you to sync gifts from EA to RENXT. It would be helpful the option to push giving history to EA as well. It says you can map gift queries and gift lists from RE, but the only endpoints in EA are for people.
Within the EA API, there are endpoints for posting contributions and bulk uploads, implying that Omatic could implement this feature to create a true bi-directional sync.
https://docs.everyaction.com/reference/post-contributions
https://docs.everyaction.com/reference/bulkimportjobs3 votes -
Review menu scrollbar
On the review menu it is a mild inconvenience to have the scrollbar all the way at the bottom, would be awesome to have it available at the top or at any moment in the review screen to see the fields
1 vote -
tabs
More Tabs! I'm ok with having an "All Formulas" tab, however I like to have one tab per vendor, and I can't do that now.
1 vote -
Attribute Comment Updating
When Importing Attribute if match on Category and Description is found, it would be very helpful to be able to keep existing comment and add to it. example we store education attribute sport with years of participation in the comments so if category=sport and description=basketball and comment is 25,24 I would want to add 26 to comment, to read 26,25,24. Perhaps concatenate existing value & add 26 with comma separator.
1 vote -
Ability to increment numbers
Ability in transformation to increment numbers. Use case: Automatic batch number IDs, etc.
and/or add ability to current calculate (we have a calculate transformation to add/subtract set numbers. We can't increment using it, though.)1 vote -
Ability to import gift note
Currently I cannot import a flat file of gifts into an NXT/webview batch because I want to add a gift note.
1 vote -
Add Custom Fields to the Fundraise Up Connector
Custom fields in Fundraise Up hold very important information that allows us to easily integrate this data into Raiser's Edge NXT. Before the connector we were able to pull this information in via the flat file and not having these fields makes it difficult to get our full set of gift data when we import.
6 votes
- Don't see your idea?