Omatic Cloud
296 results found
-
Omatic Data Service
We currently have a subscription to Omatic Data Service with IOM to find fuzzy match duplicates during import. This service has been critical in reducing the number of duplicates created in the database. Will ODS be available in IOM+? I'm concerned that duplicate records will start to increase without it. This becomes a big issue after year-end when preparing tax receipt letters if donors have gifts spread over multiple records.
2 votes -
Include Marketing Source Code and Receipt Stack
Please include the following fields for mapping:
- Marketing Source Code
- Receipt Stack3 votes -
Autoreprocess on Destination Exception Queue
It would be helpful to have retry/resend logic on records in the destination exception queue.
Examples: running Classy Recurrings Gifts and Classy Transactions on a continuous schedule, API limits exceeded, etc. This would be very help especially for clients that have to link records to parent records but want continuous functionality.
3 votes -
Additional Object Picker Field Access for Contact Roles
It would be great to have access to additional fields on the object picker when creating Contact Roles in Salesforce. This would allow for the prevention of duplicate Contact Roles being created in Salesforce if a Contact Role already exists for a Contact on an Opportunity.
Our integration is set up to create a TeamRaiser Participant Contact Role in Salesforce in order to soft credit a person who is fundraising and receives a donation. When a person donates to his/her own fundraising efforts, a donor Contact Role is created (as desired) for that person along with a second Contact Role…
1 vote -
1 vote
-
Omatic Actions Sync in RENXT from Omatic Cloud to RENXT WebView: Custom fields with a value of a Link to a record
Omatic Actions Sync in RENXT from Omatic Cloud to RENXT WebView: Custom fields with a value of a Link to a record
As you are moving away from DB view, so will Omatic move away from using Profiles in the IOM Database view system. It will start using the cloud version which connects to RENXT Web View.
In DB view you can add Actions with Action Custom Fields that connect to records. I am expecting that this functionality will also be available soon in the Cloud API for Omatic. It is not currently available.
Please make sure that this is…
2 votes -
Add connector for RENXT and Cvent
Add a connector for RE and Cvent to capture new/updated contact and consent updates and event campaign outcomes.
3 votes -
Related Record Queue Display
It would be helpful to see all records in the Related Record Queue by page rather than a scrolling view. This will make review of records faster and more efficient.
1 vote -
Partial string 'Replace' transformation
It was a sad day when I realized that there wasn't a Transformation for address abbreviation standardization like there is in IOM (https://support.omaticsoftware.com/s/article/RegularExpressionDictionaryforAddressAbbreviations) and sadder still when I learned that I couldn't create a transformation of my own. While the 'Replace' transformation will IDENTIFY a field value containing a qualifying text string just fine, it will also replace the ENTIRE field value (not just the identified text string) with whatever replacement value you designate. Thought you could use a transformation for common address standardizations like replacing "Street" with "St"? Think again, because the way it exists now will…
4 votes -
Allow import or update of gift reference on existing gifts
Allow us to import updated gift reference data on existing gifts
3 votes -
Child object matching on address in Salesforce
Currently, address is not a child object in Salesforce, so when address fields are mapped, address data can be overwritten or duplicate contacts can be added when addresses are different (depending on matching criteria). Child object matching on address would help address this issue.
0 votes -
ZIP code matching in Salesforce
Currently, 5-digit ZIP codes and 9-digit ZIP codes (where the first 5 digits are the same) will not match when attempting to match incoming records using address as matching criteria. This allows duplicate contacts to be added to Salesforce since Omatic does not match on the address when ZIP is one of the address field criteria.
0 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 -
Would like the ability to apply communication preferences in Encompass to the sub community where the email is sent out of.
have global categories at the root level, permissions for these categories are sub-community specific. This means that updates to categories at the root level do not affect sub-community levels
1 vote -
Add percentage of match results to ready buckets
The older version of Omatic Cloud displayed the percentage of matching information between records in our systems (Altru and Constant Contact). This was very helpful to us as we could minimize the amount of data being sent by only sending records with a percentage match under 100%. We would love to have this feature available again.
13 votes -
1 vote
-
Show Run Schedule in History and current last run date
We do not have a way to know what date/time range was used on any formula run. Also, we don't have visibility into the latest last run date. We are encountering issues with too much data being synced over and do not have dates/times to easily troubleshoot.
1 vote -
Include All Mailchimp API options - Member management
Mailchimp matching on email address sends an exception when Omatic Cloud - RE has a new email address for an existing contact in MailChimp
1 vote -
Formula type "BBCRM Constituents to Luminate Group" improvement
Currently when using this type of formula, the records need to be loaded to LO group all at once (automatically or send from Ready bucket).
My suggestion for improvement is to make the formula only rebuilds the group on each “fresh” run (at scheduled time), so we can process 1:1 match or 1:many match. Because we can not expect records in CRM and LO are perfect match at all times.
1 vote -
Fuzzy text string matching
Human beings are imperfect and ever-changing, and I expect OC to accommodate that variability the same way IOM does. If OC cannot find a potential Constituent or Relationship match between nearly identical strings like "Rachel Bailey" and "Rachael Bailey," then I'm forced to use IOM until it does. In the meantime, my organization is paying extra for a software that creates multiple duplicate Constituent, Relationship, and Address Records. See also https://omatic.uservoice.com/forums/950413-omatic-cloud/suggestions/46745101-allow-matching-on-fuzzy-address-formats
5 votes
- Don't see your idea?