Omatic Cloud
270 results found
-
Classy Attendee Connector
I need a connector that pulls attendee data from Classy events.
0 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 Delete button to "Multiple matches & data differences" queue
Currently, there's only "Review" button. If the record comes several time, you have to go to each "Review" screen to delete the repeats. It really takes time if there are lots repeated & records.
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 -
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 -
Pull All Records Through BBCRM Query
Ability for all records to be pulled through BBCRM
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. -
Add a Constituency to BBCRM Mapping Formulas
I would like to suggest the ability to bring in constituencies for new records in our BBCRM constituent revenue type.
0 votes -
Every Action Enhancement: Add Origin Form Name
Can we please add Origin Form Name as a mappable field in the Contributions endpoint for Every Action?
0 votes -
Seeing scheduled dates and times easily
Be able to see scheduled date and times for all formulas on integrations/formulas page.
0 votes
- Don't see your idea?