Omatic Cloud
15 results found
-
Which FE NXT batch(es) errored out?
With the new batching mechanism that can generate multiple FE NXT journal entry batches at once, we need the ability in the error text file to identify problematic batches. That way, we can delete those and leave the rest. Right now, it’s hard to tell which batches are broken.
1 voteWe already have plans to update error messages when a journal entry cannot be created and FENXT returns an error to include the Batch ID in the error message so that the user has more information.
-
Multiple Route to Ready Criteria Options
It would be helpful to have the OR operator for "Route to Ready" based on critera.
Ex: If Classy ID matches, Route to Ready
OR
If First Name/Last Name/Email matches, Route to Ready
3 votes -
ability to select what fields are updated separate from mapping/matching fields
It would be helpful if we could use fields for matching but then select which ones we actually want to be updated.
For example, match on name or Constituent ID/Donor ID, but only update the email address or web appeal activity information.3 votes -
Add ability to route to "ignore" and filter records from processing
When building a formula, it would be extremely helpful to define a set of criteria or matching rules that would automatically route a record to Ignore or a queue to Confirm Ignore.
3 votes -
Enable Short vs Long Formatting for Address Lines
Currently, the replace function will impact the entire string. Example: When formatting an address, 111 West 3rd Street, I want to replace West with W & Street with St. In this scenario, the current functionality will give me an output of “W”. I would like to request the functionality to replace individual elements of a string. Example: When formatting an address, 111 West 3rd Street, I’d like to replace both West with W and Street with St, giving me an output of 111 W 3rd St. Without this additional functionality it is impossible to keep aligned with our database standards…
26 votes -
Seeing scheduled dates and times easily
Be able to see scheduled date and times for all formulas on integrations/formulas page.
0 votes -
Send to a specific triage bucket based on a Mailchimp status field results returned during matching.
Triage currently takes specific match situations into account but I'd like to send records where Mailchimp returned "Cleaned" or "Unsubscribed" directly to the Exceptions triage bucket regardless of matching criteria. This will allow me to automate the Ready triage bucket instead of needing to review it before sending the record updates to Mailchimp. This matters because I'm trying to reduce the overall number of API transactions (Blackbaud has a threshold over which they charge me extra).
1 vote -
Title part of data differences
Can you make Title part of the data differences options in routing/matching?
3 votes -
Name fields from Stripe to populated
Stripe specific parsing reques
3 votes -
HubSpot Email Information Subscription Dates
It would be very helpful to have Subscription status > history > dates available in the HubSpot Contacts formula. This would allow us to bring in more accurate data when managing email subscriptions
8 votes -
Custom routing of records
Sometimes records need additional review steps and currently we are capturing those notes in an email/document to work through outside of the formula. We think Custom routing of records may help with this as it would allow us to set criteria (or decided on the fly) to route records to a special bucket, for instance, to review later. This would be a time-saving enhancement.
9 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!
-
Add option to skip New User Creation
In certain cases, there are reasons that if no user is matched it would be more applicable to skip that user rather than have new users created. It would be nice to add the option to automatically skip/ignore New Users. Currently they do go into a new user bucket, but we have to manually go in and repeatedly empty the bucket.
3 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 -
Add option for formulas to consider null vs non-null a match
Currently if a mapped field is configured to be checked for data differences and that field is NULL in either the source or destination record but not the other, the field is flagged as a data difference. In some formulas it would be nice to be able to choose whether to consider NULL vs NOT NULL as a match for each field instead of always defaulting it to a data difference. This is especially relevant when matching on Altru Alt Lookup IDs since those will often be NULL in Altru until they are first populated by an OIC formula.
0 votesThanks for bringing this to our attention! We've got this on the slate to be researched, along with other ways we can improve the handling of common/consistent Data Differences.
- Don't see your idea?