Omatic Cloud
414 results found
-
Ability to map Luminate online cross references via API in the Omatic Cloud
Luminate stores values here for its web services and accessing them would make for more efficient, straight forward mapping in the Omatic formulas. Specifically, these cross-reference types would be most helpful to CHLA:
- Donation Form Cross-Reference
-Donation Options and Designations
-TeamRaiser Cross-Reference
Navigation in Luminate Online: Data Management / Import/Export / Cross-Reference Types0 votes -
Matching records in Ready/1:1/1:N WITHOUT it updating the other system
For example, in a Mailchimp to Raisers Edge connection, there should be an option when setting up a formula to use items for matching but that doesn't meant when the records are matched that Mailchimp updates RE.
For instance, we have a lot of couples in our database, but they have separate emails so they have separate Mailchimp records. If somehow during triage/Needs Attention I miss that the names are different, or they go through to the Ready bucket and I miss it, then RE has been updated to 1 person's name thereby messing up the database.
0 votes -
Filter function in 1:1 and 1:N
It would be wonderful to be able to not only discard/ignore certain records below a certain threshold, but it would be super helpful to add a filter function to the MATCH column to be able to filter by what the records are matching on. i.e. only pulling up those records that matched on Email, or Email and Name. This would be particularly helpful for the Mailchimp to Raisers Edge and vice versa formulas.
0 votes -
Enhanced override button functionality
Whenever the override button is utilized to match to an existing CRM record, Omatic does not provide the opportunity to select data that may differ between the LO record and CRM record before confirming the match (as is the case when utilizing "match" button). Is this something that can be addressed in the future?
Currently, source data overrides destination data when you using the match override; which trigger the need to update records manually outside of the Omatic Cloud so being able to see the data differences for match overrides to pick whether to keep destination data or use source…
0 votes -
Build a suppression that does not rely on an Luminate Online group
Currently we use LO group (query based) for suppression in formula 1 to exclude undesirable records, records only have name and email, records come from facebook signup/donation, etc. However, there are 2 major limitations to these query based LO groups:
Query tool in LO has a very limited selection, and we can not access and use
'Last Modified By' field. The reason we want to use that field is:
a. Users (admin) need to update records in LO: merge, update bio info, etc.
b. Background processes also update LO records: calculate Engagement FactorGroup can only be rebuilt Once per…
0 votes -
Being able to stop a file while it is running
When you go into integrations/Formulas and press "Run Once", being able to cancel that after you "Run Once" would be extremely helpful.
0 votes -
Delete from queue when Ready
I have a formula to look at Mailchimp activity and add a Mailchimp ID Alias in RE/NXT. In the Triage rules, if there's a 1:1 Match on only this alias it goes into the Ready bucket.
My current options for the Ready bucket are to hold for review or immediately send the alias into RE. Because it's already there, sending it again doesn't make sense. I'd much rather Delete anything that gets into that Ready bucket because the relevant data is already there. Am I missing something?
2 votes -
Create Email Activity When Using LO Email Activity Formula
Currently the LO Email Activty formula creates an action in the constituent record. It would be great if, instead, it created an entry in the Email history tile instead. We would like to reserve the Action tile for more personal, one to one communication and record the bulk emails in the Email history tile.
0 votes
Emily Dalton
responded
I agree this would be a great idea! Currently we are limited by the RENXT API"," and not able to send data through the API to the Email history tile. If this becomes available"," we will add this ability to Omatic Cloud. -
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 -
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 -
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 -
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 -
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 -
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
- Don't see your idea?