Omatic Cloud
211 results found
-
Allow formula to run against all dates
We use a constituent formula to sync RE NXT records to LO Donor Groups. Currently, the formula will only sync records modified within the past 30 days, but we may have thousands of records not modified in that date range that still need to be in a particular donor group. Forcing a change in the modified date just unnecessarily increases the volume of records also synced by the Opt In formula. We would like to be able to choose to run the formula against all dates.
5 votes -
Ability to remove special non-ASCII characters aka Emojis
It would be helpful to be able to remove nonstandard characters or Emoticons using the "remove custom text" field.
Use Case - Email subject lines often include these unreadable/unusable characters.
5 votes -
additional -- useful -- logic operators in P2GL
Can we add some additional -- useful -- logic operators to P2GL?
*Blank
*Not Blank
*Does Not ContainBlank and Not Blank are especially useful. Today, without them, we're forced to use 'Equal' or 'Does Not Equal' and then compare that to an unpopulated field. Sometimes, however, if there are spaces in a field, it might look to be blank but isn't really.
All and all, it's just safer and more efficient to have 'Blank' and 'Not Blank' operators.
'Does Not Contain' is useful for working against alphanumeric data, and would prevent needing to use more complicated 'If/Then' or 'True/False'…
5 votes -
Separate formula Type for HubSpot Email Subscriptions
Currently, the HubSpot formula "Contacts" handles all subscription information. Could this information to be handled separately in a stand alone formula since the "Contacts" formula handles all changes, not just email subscription changes.
The current process is noisy and creates a high volume of records that are unrelated to email subscription changes. This is also problematic for the HubSpot connector given API hits.
4 votesWe are planning to add this feature in Q4 2023!
-
SF Leads Matching on Contacts and If the Contact does not exist create a Lead
When attempting to add Leads to Salesforce using the Any Objects Formula, we would like the ability to look for Contacts first to see if a match exists. if no contact is found we would like to add them as a lead.
Use Case: When bringing in a file of Leads they may or may not exist in SF. If they exist as a contact in SF we would not want that lead to be created. If no contact is found we would like to have them as a lead rather than a contact.
4 votes -
Allow for defaulting Recurring Gift Fields on a Gift when Bringing in Recurring Gift Payment
When bringing in a Recurring Gift Payment to RENXT I would like the ability to default the fields on the Orginal Recurring Gift. This includes bypassing the error message that Fund ID is required. If the Fund is not populated I would like to populate the Fund with the original recurring gift.
4 votes -
Classy Transaction Filters
I would like to include the following filters in the Classy Transaction Endpoint:
- Company Gifts based on if Company is provided or Individual Gifts Based on if Company is not provided.
- Only Recurring Donations or Only Individual Gifts
- Status: Include Succesful or Pending(ACH)
- Date filters Refund Date, Date Modified, Date Added, or Payout Date.
4 votes -
Another User Role for Running Formulas
There is a User Role in Omatic Cloud for "Formula Producer" that grants "the ability to create, run, and modify all the formulas".
It would be nice to have a role for only running a formula. There are times we want someone to be able to run a formula, but don't want them to edit it.
4 votes -
Add Ability to import Tributes to RENXT
We would like to import Tribute Data through OC, into RENXT.
4 votes -
New Records bucket matching
If multiple rows come in for the same person and are routed to the " New Records" bucket because a match is not found in destination, clicking "Send All/Page" sometimes creates duplicate contacts/constituents. We need matching capabilities in the New Records bucket to prevent duplication if all bio data matches exactly.
Currently, the work around is to ensure a unique ID is populated, so that any new records that are duplicates will be sent to exceptions. Those exceptions then need to be reprocessed in order to match. However, this only works when a unique ID field is available from the…
4 votes -
More intuitive relationship matching
Relationship matching and routing works great IF the primary constituent mapped is already in RE.
If the constituent is BRAND new then you are forced to go through the entire data flow for relationships even if the relationship is already in RE and is a 1:1 match. Meaning many unnecessary and inefficient additional clicks.
4 votes -
Add default data difference option to Ready
Ready bucket currently defaults to source for any data differences. Add ability to choose source or destination for data differences so when send all or send page is selected, we have control over what is retained in the destination.
4 votes -
Add Classy payment type filter during import - paypal vs. stripe
The ability to import paypal gifts only and then stripe gifts only would significantly help during import and reconciliation
4 votes -
Dedup records in triage buckets
I'm finding duplicate records within formula triage buckets which means I either need to process or manually delete each of them. I understand why they sometimes occur but would like within the Reprocess functionality or as a separate action button the ability to remove duplicate records.
4 votes -
RENXT Gift List Formula Type
We would like to have the formula type RENXT Gift List > HubSpot. This would allow for relevant gift information to be transferred back in to HubSpot to determine the ROI on email campaigns.
4 votes -
Make lookup fields external ID friendly
Lookup fields, prior to expanding the object, will only accept the Salesforce GUID, currently. If we want to map to another field, we need to expand the object. Having the lookup field accept any external ID of that object would aid in preventing too many objects mapped and also help to prevent unnecessary related records match work.
4 votes -
It would be an improvement if we could have Payout date as an option for mapping.
When bringing gifts over from classy the GL post date is not matching our deposit dates and this is causing issues with finance. If we had the ability to map the payout date to the GL post date that would make the financial process cleaner and much smoother without manual global changes.
3 votes -
Ability to review all data being imported
Any field that might be touched through the Omatic import should be displayed on one screen to be approved by the importer. The current data difference grid only shows a couple fields. We should have the ability to see the two side by side (current BBCRM data & new Form Data) and decide which to keep untouched, and which to update with new data, and also have the ability to make edits to the new data before import.
3 votes -
Provide the ability to overwrite an existing value with a null value in MailChimp
Currently, date fields with null values are not sent through the MC connector. I'm not sure if this also applies to other types of fields.
This means that if a date field is populated in MC, then updated to a null value in RE, the date will not be overwritten in MC with the new value.
Because we use these date fields (expiration date, date joined, etc) as segmentation criteria, this affects our marketing campaigns to targeted audiences and can cause significant problems.
3 votes -
Have an export profile in the LO Connector that allows for TeamRaiser registrations to be exported from RE to LO.
Omatic has gotten TeamRaiser donations to flow really well from Re to LO, but the missing piece is still the offline registrations that need to go from RE to LO. Currently we have to use Blackbaud's arcaic upload system and then still rely on RELO to pull them down into RE because the import for registrations either does not have the ability to recognize offline registrations or cannot recognize the time stamp the LO uses for offline uploads of registrations.
3 votes
- Don't see your idea?