Omatic Cloud
296 results found
-
Formula Triage Summary - Column Headers
It would be nice if there was a way to tell which of the "Add if not matched" and "Edit if Not Match" headers go to which section. I understand that by default they are meant to be in order but it still can be somewhat confusing on larger formulas. Not sure if color coordinating headers would be a simple solution, or maybe a tool tip containing the section name?
1 vote -
Add Event Registrant Attribute to Cloud import
Would like the ability to map and add an Event Registrant Attribute in BBCRM.
0 votes -
Update existing records only - do not require mapping Constituent fields
When using Alias as another unique identifier to import from another platform, we need the ability to match on Alias without matching on any other pieces. At this point, a top object within the Constituent section needs to be mapped in order to create a valid formula.
0 votes -
Allow Multiple Instances for the Classy Connector
I have two different Classy for two of our affiliate organizations and we have to bring in transactions from each affiliate separately. It would be nice to be able to bring all transactions from both affiliates in one profile.
0 votes -
Ability to add financial account info to recurring gifts (BBCRM)
We currently do not have the ability to add financial information for recurring gifts. We have a file with a mixture of Credit Card and EFT recurring gifts and we are unable to populate EFT information in the recurring gift. We would also like the ability to add new financial relationships if they don't exist on the record also
0 votes -
Access to Email History/Event Registration in NXT
We would like to use Email History in NXT to help determine some engagement factors in Luminate Online on a constituent record. Currently there is no way to map/transform/capture that information.
With the new iOS privacy update, understanding constituent engagement and having a 360 picture of engagement across all platforms is incredibly valuable. We would like to explore accessing those fields to apply an engagement number in LO. In addition, if someone registers for an event in NXT, that should be applied to a different engagement factor field.
0 votes -
Convert old last name to an Alias when adding new
When pushing the Last Name field to BBCRM, it would be more beneficial to have the old last name converted to an Alias rather than simply overwriting the field.
0 votes -
Add ability to export membership data out of RENXT
We were hoping to be able to push data into Raiser's Edge NXT surrounding membership. We would need:
Membership Category
Date Joined
Date Expires0 votes
Emily Dalton
responded
Currently these fields are not available in Blackbaud's SKY API. However"," once they are available"," we will look into adding this information! -
Additional highlighting in the queue grids
When viewing the queue grids, we would like to have the changed values highlighted across the queue grids. Currently, only the first two columns are highlighted, Luminate and BBCRM.
0 votes -
Do not match to inactive records
When matching incoming records through Omatic Cloud to RE, the system should not match to inactive RE records. Or at least add the option not to match to these record types.
0 votes -
LO e-commerce formula type
I would like to build an e-commerce formula in Omatic cloud and split gifts by item
0 votes -
Add Delete button to "Multiple matches & data differences" queue
Currently, there's only "Review" button. If the record comes several time, you have to go to each "Review" screen to delete the repeats. It really takes time if there are lots repeated & records.
0 votes -
Ability to modify new or existing records
Ability to choose if I want to make modifications to an existing records while making different modifications to new records all through one formula that are sent to ready. Example: having new records mark new email as primary while existing records do not mark as primary or overwrite.
0 votes -
Update fields with blank values
We would like to have the functionality for Omatic Cloud to update fields with Blank values in from Luminate --> Salesforce and vice versa from Salesforce --> Luminate. Blank values have meaning in both of our databases so this functionality would be extremely useful.
0 votes -
Export Matches
Would it be possible to allow for exporting the grids from 1to1 or 1 to Many. This would be helpful for when the list could use more insight and the list should be sent to someone else. For Example, between 2 systems it is common for potential duplicate users to be identified and land in the 1 to Many. When this happens, we would like to export the list to send to the team leading that system so they can address that the potential duplicate. During larger groups of records, this list can be larger and is easier to sift…
0 votes -
Add "Send to Needs Attention" button in Ready Bucket
Similar to adding an Override button to the Ready bucket, similarly it would be nice to have a "send to 1:1" button when filtering through those matches in the Ready bucket.
0 votes -
Ability to Auto-pick on First/Last Name OR Organization Name
Currently with Mailchimp and RENXT integration formulas, auto-pick only allows to either match on first name/last name or organization, not both at the same time. It would be more helpful to be able to pick all first name, last name, and org name instead of having to pick one, and have the other go into 1:1 bucket instead of Ready.
0 votes -
Conditionally Ingore Records
I would like to pitch an idea to conditionally ignore entire records based on a specific field value or set of values. For example: - If a specific field is of type date and a specific date is found then that record would be ignored. - If the profile field "Marital Status" is equal to married than ignore - If the specific value matches the same field in the destination source, then ignore the record
1 vote -
BBCRM > LO Formulas - Would like additional fields such as address data to be returned for matching.
Currently in BBCRM >LO Formulas when matching records,the address info does not appear in the grids so we can't use that to decipher what the correct matched record is without going into each potential match which is very time consuming. Mailing address would be helpful for the following reasons: 1) LO and CRM may have different emails for a same person (with same address). 2) LO may have duplicated records for a same person but the system can't tell they are duplicates. E.g. - Incoming CRM record (same name) mailing address match one LO record and email address match another…
0 votes -
Request to have TeamRaiser revenue formulas mimic the same behavior as non-TeamRaiser formulas when it comes to revenue exclusion.
Hi Omatic Team, Formula type: TeamRaiser Registration and Donation to BBCRM Constituent/Revenue & Luminate TeamRaiser Donations to BBCRM Constituent Revenue
Request to have TeamRaiser revenue formulas mimic the same behavior as non-TeamRaiser formulas when it comes to revenue exclusion. Currently, we can exlucde "offline" gifts from coming over via our Revenue formula (type=Luminate DOnations to BBCRM Constituent/Revenue),
but this behavior is not consistent with TeamRaiser revenue formulas. While we have safeguarded these from coming over to CRM, it would be more user-friendly to not see them in queue at all.0 votes
- Don't see your idea?