Omatic Cloud
9 results found
-
Make column order in data grids "sticky" per user
Currently in Omatic Cloud data grids, users can click and drag the columns to the right of the action buttons to re-order them. However, upon leaving the data grid and returning to it the columns reset to their default order (alpha by field name). It would be nice if Omatic Cloud would remember custom column order for each formula for each user. There are many times when it is helpful to refer to specific fields in the data grid when choosing whether to add, match, or delete a record but those fields are way off to the right. So it…
22 votes -
Option to get user input when incoming data doesn't match existing data for specified fields
We often have enough information to be confident that the incoming data matches a record in Salesforce. However, whether the better quality data for important fields is in Salesforce or the incoming data is unknown. So we can't confidently overwrite data without a manual validation.
For example, P Ennals might match to Peter Ennals. I am happy this is a valid match and therefore want to set it as a ready record. However, I don't want P to overwrite Peter.
The functionality could be such that I specify per formula which fields require manual validation. E.g. for records where name…
6 votes -
Allow formula to run against all dates
We use a constituent formula to sync RE NXT records to LO Donor Groups. Currently, the formula will only sync records modified within the past 30 days, but we may have thousands of records not modified in that date range that still need to be in a particular donor group. Forcing a change in the modified date just unnecessarily increases the volume of records also synced by the Opt In formula. We would like to be able to choose to run the formula against all dates.
5 votes -
Ability to ignore a record
When pulling data into SF there are times when a user wants to ignore or skip a record and not pull it into SF. Use case for this is a list of contacts or oppts with a field value that indicates they are not valid or at the level required for adding to the SOR.
3 votes -
Make unmapped fields used in Record Match Search available in Summary Grid View
address, email, and phone are all helpful in identifying matches, but unless the fields are mapped, we can't access them in Summary Grid View. Please also allow fields used in Record Match Search to be added to grid view for ease in identifying correct matches
3 votes -
Add ability to filter transactions from Engaging Networks
It would be nice to be able to filter incoming Engaging Networks transactions by the status. The status being returned from Engaging Networks is either "success" or "reject" and we'd like to be able to filter the declined, or rejected, transactions.
3 votes -
Post to GL outputs for FE NXT
The formula template for posting to FE NXT does not furnish any options for the output files that the formula generates (other than the actual batch in FE NXT). Since a Post-to-GL user may not have direct access to the destination FE NXT system, those output files are very valuable for analysis and troubleshooting.
Currently, they come out as .txt files, which makes analysis challenging even when using an advanced editor. Can the output file that represents the created FE batch be output in .csv format? Or, could the user building the formula be given an option for the format…
1 vote -
Automatically delete $0 "donations" when importing
Third party workplace/matching gift platforms (i.e. Benevity) will often provide import documentation that contains either an individual contributions OR a company matching gift - leaving the other field to contain a $0 "donation."
When uploading those files through Omatic Cloud - the $0 "donation" is pulled into the "Needs Attention" queue and require the user to manually delete.
Omatic should create a functionality that would allow users to set conditions in their formulas to automatically delete these $0 "donations."
1 vote -
Additional Filtering for HubSpot connector
Allow for filtering contacts based on lists/or properties of the contacts. Example: Organization is sending emails to both donors and program participants. They don't want to import program participants into RENXT but also want to reduce management of formulas and continually updating Source settings.
0 votes
- Don't see your idea?