Omatic Cloud
390 results found
-
Record Routing / Advanced Matching Working Together
Currently, if Advanced matching settings are enabled, it interacts with routing in a way that unintentionally disrupts routing to ready based on Primary match. It would be helpful to include "Primary" matching in routing rules. Due to the current interaction, it probably wouldn't be recommended to use primary matching on one field if the route to ready rules are based on multiple fields.
1 vote -
Phone format for UK
In ImportOmatic with the dictionaries we had ability to check if the phone number was less then 11 characters and add a '0' at the beginning of the string
1 vote -
1 vote
-
Add a DonorDrive bi-directional workflow from SOR>DD
The Native DonorDrive connector with Salesforce is bi-directional, allowing the syncing of constituent/contact updates from NPSP/NPC to DonorDrive
1 vote -
Record match search
It would be helpful to also have the option to include a LinkedIn url address as an option for constituent match search for imports.
1 vote -
Option to add mapped data only if records are new
We have a couple one off scenarios where we only want to bring over information IFF the record is a truly new record in BBCRM.
For example: addresses, BBCRM is usually the most accurate in terms of our data. While we have some "Add if not matched logic" we often run into the flags being set to false for new records.
So it would be nice to have a blanket "Always add address for new records"
1 vote -
Post-to-GL prepost feature
Many Salesforce and Virtuous clients who have FE NXT but migrated from RE NXT are used to the 'prepost' feature in RE / FE integration.
P2GL for Salesforce or Flat File does not have a similar feature that can be used to validate a posting before it creates an open J/E batch in FE NXT. A number of clients have asked about this.
1 vote -
Upload source files directly from Integrations/Formulas page
I'd like to upload the Source files for Flat File as-a-source formulas directly from the Integrations/Formulas pages, without the need to navigate back to Data Queue page and search for my formula every time.
1 vote -
Update Matching with Encompass Connector
When going from BBCRM to Encompass Matching only allows for custom options and pre-populates with ALL currently mapped fields.
While this is trying to be helpful, if there are 30 mapped fields it will default to matching all 30. At that point it would be more helpful to not pre-configure matching and let the user configure the matching.
1 vote -
Add connector for AlumnIQ
Would like a connector for AlumIQ for BBCRM OC
https://www.alumniq.com/1 vote -
Deceased indicator
Display a deceased indicator in the data differences columns of the triage buckets, similar to displaying Mailchimp contact status. This will help with decisions without me needing to step into the record just to find out they're deceased.
1 vote -
1 vote
-
We would like the ability to sort data in the Needs attention bucket. This is the way they used to be ordered.
Previous order was:
1. 1:1 Matches
2. Multiple Matches
3. New Records
4. Destination Exceptions
5. Formula Exceptions1 vote -
1 vote
-
Include non-mapped source fields in summary fields to help with decision making.
We don't want to update fields in LO but want to see the source fields (which are not used in the mapping) in summary fields to assist in making decisions.
1 vote -
Integrations/Formulas | Mapping | Total Sum of Two Cells/Columns from an Import File
Built-in feature that allows combining two column headings to create a total sum during the mapping process.
Example: scenarios of summing platform fees and transaction fees.
1 vote -
Mailchimp Unsubscribe Formula - campaign information missing
In the unsubscribe export file on Mailchimp, it lists the email campaign that prompted the user to unsubscribe under the 'UNSUB[underscore]CAMPAIGN[underscore]TITLE' field. Unfortunately this campaign field is currently not information available within the unsubscribe connector API. Neither is UNSUB[underscore]TIME. it would be good to be able to add this information to RE through Omatic Cloud as it is vital additional context on unsubscribes.
1 vote -
1 vote
-
1 vote
-
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
- Don't see your idea?