Omatic Cloud
326 results found
-
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 -
When copying a formula, copy all the setting of that formula (summary grid, matching settings, etc.)
2 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 -
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 -
SSO Support for SAML 2.0 or OIDC
It would be great if there was improved SSO support for Identify Providers other than Microsoft.
Maybe SAML 2.0 or Open ID Connect to enable support for customers chosen IDP.1 vote -
Log when a formula is reprocessed in Activity History
Currently the activity history does not show when a formula is reprocessed. This info would be helpful especially when working through the exceptions buckets. it would all use to better track errors that are recurring.
4 votes -
Allow formula to always send full list of constituents from Luminate Group
Right now formulas are only based on time, I would like to build very specific queries in luminate to build groups and have omatic pull all records into RE every time from a group. This is important because group rebuilding once every day, and if a new constituent is missed the rebuild the next day will catch the constituent. But since the current formulas use last run date the only way that new constituent will go to RE is if it is modified.
1 vote -
1 vote
-
1 vote
-
Excessive number of duplicates - when donors give twice within same flat file
If a donor donates twice within the same flat file, Omatic Cloud will generate duplicate records for that donor in Raiser's Edge (because it sends records all at once). In contrast, ImportOmatic sends records one at a time, so if a new donor gives twice, it will be matched the second time.
This is especially problematic for events, when a donor will both buy a registration ticket and make a donation within the same flat file. Multiply this by the majority of the attendees for the event and it results in an excessive number of duplicates. This is a big…
1 vote -
Add Ability to Clear Fields in Luminate Online
Currently, we are unable to clear fields in Luminate Online when we know data no longer exists or is inactive. It is a risk to not enable a way to clear data in Luminate Online, as the data could flow back into RE undoing the data staff changed. A null value should not clear a field, rather use a character like ~ to indiciate a field should be cleared. This should work for any data type (date, text).
3 votes -
Enhanced Mappable fields to Transformations
This was a previous uservoice story but there are still gaps with usability with the if/then ability in transformations. Specifically with if/then/else, the cascading transformations are challenging to build out for most users outside of onboarding.
The ability to include mapable fields directly to a transformation, outside of concatenated replace logic, would be very helpful and would allow for a more intuitive user experience. This is current functionality in P2GL and it would be helpful to have in Omatic Cloud as well.
3 votes
- Don't see your idea?