Omatic Cloud
381 results found
-
Recurring Gift Card Token
Ability to import BBPS card tokens
https://developer.sky.blackbaud.com/api#api=gft-gifts&operation=AddGiftsToBatch
1 vote -
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 -
Support for line break character (/n)
Right now we can add line breaks through Concatenation, but there isnt a simple way to force a line break in some more complex situations.
We use this particularly for notepad text, where we want to summarise a few cells of data into a single notepad, e.g.
'Signed up for Email Newsletter on the website. /n
First Name Provided: Alex /n
Surname Provided: Bishop-Thorpe /n
Email address provided: alex.bishop-thorpe@'Importimatic supported '/n' as a line break character, but this isnt supported by Omatic Cloud. Instead it just renders the text '/n'. If we use the line break as the separator…
5 votes -
Custom Routing to send some rows onto another Formula
Sometimes it's necessary (or more convenient) to achieve our desired outcome by taking one file and running two different Formula across it.
A common example would be files that have a mix of Individual and Organisation records. One Formula for the Individual import, and another formula to do the Organisation import - the Organisation import would add and link the individual as a Contact against that Organisation. Fancy.
Right now custom routing lets us skip some rows, having the Formula ignore them. This let's us have our two import formulas, one for Individuals and one for Organisations.
But it would…
6 votes -
Add Tax Receipt Number
Could you include the Tax Receipt Number field in the mapping? The gift transactions I import into RENXT come from an external system that has already generated the tax receipts.
1 vote -
The ability to exclude records before transformation
It would be great to be able to have a formula skip a record based on specific criteria before transformation and matching happens. For example, we have lists that contain thousands of people that get scored by a wealth screening service. We only want to import the records that have a score of 52 or higher. This is sort of like the custom routing rules that happen after all the records have been matched/transformed. But having this ability before processing skips having to deal with exceptions for records that ultimately won't go into the CRM and saving us time.
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 delete bio2 end dates
I need to be able to remove end dates from the bio2 codes. We use them to show what projects a constituent participates in.. If they sign up again after a lapse, we need to be able to remove the end date that is there.
1 vote -
Allow matching on relationship types
Relationship matching needs an option to match on the relationship type.
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.
5 votes -
Allow update to Recurring Gift Status
When a recurring gift plan is terminated due to failed payments, completed or cancelled by the donor, it is necessary to update the status of the recurring gift in RENXT.
Blackbaud's current API for PATCH Gift (Edit) indicates "Posted gifts cannot be modified, except to change recurring gift status".
Please allow for integration of Recurring Gift status updates.
3 votes -
Add individual system Record ID as a match option when importing a Relationship
Expand the matching logic for Relationships to include the Constituent System record ID . The constituent system record ID is unique across RE and is assigned to a record once added in RE. This data point will allow the import for Relationship records to use an alias/alias type and constituent system record IDs to get an exact match and will prevent duplicate/reciprocal relationships to be added in RENXT. Currently ImportOmatc will match on an Alias ID and will not create additional relationships if it exists.
Currently in OmaticCloud, matching on alias id/type will result in unwanted/duplicate relationships added to RENXT.…
3 votes -
Add Suffix as a field for matching.
We bring in many alumni or students who have parents who match on first, last, address, etc. and we would like to use Suffix as a matching or autopick field.
1 vote -
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.
3 votesHi 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…
-
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.
3 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.
19 votes -
Link Multiple External System Accounts to a Single Salesforce Account
If, over time, a donor makes gifts through Fundraise Up (FRU) using different email addresses (e.g., intially from an @aol.com account and later from an @gmail.com account), FRU will create a new record for the second gift. Because FRU isn’t a CRM, we can’t merge records. They will forever be separate with their own Fundraise Up ID (FRU ID).
When we sync records from FRU to Salesforce, we can match the new FRU account to the old account based on a name and address match. However, this is a manual process and forces us to decide which FRU ID to…
3 votes -
Shopify Connector
It would reduce a lot of manual work to have a connector to pull purchases from Shopify into RE NXT via a connector.
1 voteHi Alexandria. Thanks for your idea. We currently have the Shopify in development. It should be ready to go in the new year.
-
Pull the correct names for a tribute match
When importing tributes from Luminate Online, the tribute name pulls as the donor's name, so I have to go into the RE NXT record and the Tribute donation interaction to see the incoming data and match it to existing data. Once the tribute goes into RE, the Tribute name shows as the correct tribute name indicated on the form, so it would be nice if the correct name showed up on the import screen.
1 vote -
View API Name in Object Picker
When selecting fields in the Object Picker, some of them have the same label but different API names. For example, we can have City (MailingCity) or City (City_Employer). It would be extremely helpful if we could hover over the field and see the actual API name to ensure we're mapping to the right field, rather than needing to do a lot of trial and error testing.
2 votes
- Don't see your idea?