Omatic Cloud
269 results found
-
Date Cleanup Format in mapping for Unix timestamps
We have a handful of connectors, example Hubspot, that save dates in a Unix timestamp format. A cleanup for date fields that will automatically changes dates to this Unix timestamp format would be helpful when integrating with these connectors. This will reduce destination exceptions caused by date format issues.
2 votes -
Print out P2GL formulas
Currently there is no ability to print out P2GL formula configuration or logic threads. Since formulas cannot currently be copied, they have to be replicated manually and the inability to print formula configuration tremendously hampers that effort. This is even true when working to apply logic from one client's formula to another -- since the logic thread cannot be printed, it's challenging to recreate from memory and/or to toggle back and forth between formulas/monitors, etc.
2 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 -
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 -
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. -
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 -
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
- Don't see your idea?