Omatic Cloud
211 results found
-
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 -
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 -
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 -
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 -
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 -
Add Event Registrant Attribute to Cloud import
Would like the ability to map and add an Event Registrant Attribute in BBCRM.
0 votes -
Export Formula Mapping and Settings
I would love to see an option to export the formula mapping and settings like we can for Omatic profiles. I keep a file with the mapping of the most recent versions of my profiles. That way, I can refer to it as I'm building new and similar profiles and have it as a backup in case I inadvertently mess something up. I like the ability to download to excel but a summary or review screen would probably serve the same purpose.
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 -
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 -
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 -
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 -
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 -
Promote Changes from Sandbox to Production on Existing Formulas
Currently Omatic Cloud offers the capability to Promote the Sandbox formula to Production once. If adjustments are made to the formula later (ex: a new field is added) there isn't a way to push that update to the Production formula. The Prod formula has to be deleted and then the Sandbox formula can be promoted again. I would like to request the ability to promote changes from the Sandbox formula to the existing Production formula. This would eliminate the need to delete the existing Prod version. It would also encourage changes to be made and tested on the Sandbox formula…
0 votes -
Add Formula Name to the Delete Formula Advisory
When deleting a formula there's an advisory message to confirm deletion. It would be awesome if the formula name appeared on the advisory so we can visually confirm we're deleting the right one. Similar to how when you're promoting a formula to Production the name is displayed.
0 votes -
Archiving constituent attributes when changed by ImportOmatic
This is a bit of a pie-in-the-sky (and specific) dream, but I'm going to put it out there nonetheless:
We use Omatic Cloud to update values in an already-existing Constituent Attribute category. Currently, we can use Omatic Cloud to update the Constituent Attribute if the import has a different value than the existing value in the record. However, we want a way to archive the previous value when it is replaced (like how in ImportOmatic, old addresses can be switched to a different category when a new address is found). We've been able to build out a workaround by adding…
0 votes -
Omatic Cloud Encompass Transactions Merchant Account Filter
We need a filter added to the Encompass transactions cloud connector to be able to filter by merchant account when creating a new transactions profile. It would be in the dropdown for "Do you need to filter the incoming data".
0 votes -
Additional Filtering for HubSpot connector
Allow for filtering contacts based on lists/or properties of the contacts. Example: Organization is sending emails to both donors and program participants. They don't want to import program participants into RENXT but also want to reduce management of formulas and continually updating Source settings.
0 votes -
Add Payout ID and Date to the API
Payout ID and Payout Date added to the API for reconciling between P2GL and OC integration. It's a critical information requirement.
0 votes -
Field Campaign Internal Name Visibility
Ability to view the Internal Campaign name in hosting when attempting to map Classy Recurring gifts,
0 votes -
Pull All Records Through BBCRM Query
Ability for all records to be pulled through BBCRM
0 votes
- Don't see your idea?