Omatic Cloud
388 results found
-
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 -
Advanced address processing screen in the Omatic Cloud is needed
We need an advanced address processing screen in the Omatic Cloud. Right now my choices are to import addresses without knowing if they are valid, or ignore addresses We also need to be able to update a new address while saving the old address as a former address. Why? People enter their addresses online incorrectly and sometimes on purpose. (I've seen people who don't include their house number or apartment number, or enter "nowhere" street.") If I allow address information to come in that doesn't match to their current address I could be overwriting good address info in RE with…
225 votes -
allow to import non-constituent participant records
We would like to be able to load non-constituents into events as participants via the cloud integration.
20 votes -
Ability to map Action Notepad Type
When importing CC data into NXT via Omatic, the default for Action Notepad Type is "Added via Web View". This default is not effective in allowing us to report to our Board and stakeholders outcomes. After uploading actions we will have to manually change this field.Having the option to define or map this field will give us richer data and better metrics to report on.
4 votes -
Add ability to only add certain mapped fields to new records
We would like to be able to decide specific criteria only applicable for new records added, not existing. Similar to applying default settings to new records in Importomatic.
Examples:
-Add addressee/salutation styles to new records
-Only add constituent code to new record
-Only add preferred name to new record107 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 -
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 -
Have a repository for transformations
Can we have a have a repository for transformations so we don't have to rebuild and maintain them on different formulas? That would save a lot of time and double checking. Thanks!
197 votes -
Add additional "Actions" to Ready Bucket
Have the other actions that you can do in Needs Attention available in the ready bucket (ie. The Add, Override and Delete button).
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 -
Add ability to specify the Constituent Code sequency (Primary Consituent Code) when adding or editing
Blackback RENXT considers the first or top Constituent Code on a constituent record to be the primary code. This primary constituent code is automatically used in reporting and is the default on new gift records.
We are requesting the ability to specify if a constituent code should be in the top spot when importing (creating or editing) a constituent record.
The skyapi for constituents allows a sequence to be specified when creating or editing a constituent record however Omatic Cloud has not exposed access to specify a sequence value.
The current behaviour appears to add a new constituent code to…
5 votes -
1 vote
-
1 vote
-
Reprocess without Re-matching
Currently, when editing a formula you need to reprocess the data for the changes to take effect. What would be nice is there was an option to reprocess the data without needing to do the rematching.
For example, I edited a transformation after pulling in 100k records. Specifically updated the comments which is Defined not matched. Another example would be updating a transformation on a field that is not being matched by or routed by.
So essentially is an field is not being used to match or to route, then there is no reason to have to re-do the record…
4 votes
- Don't see your idea?