Omatic Cloud
22 results found
-
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 -
Make lookup fields external ID friendly
Lookup fields, prior to expanding the object, will only accept the Salesforce GUID, currently. If we want to map to another field, we need to expand the object. Having the lookup field accept any external ID of that object would aid in preventing too many objects mapped and also help to prevent unnecessary related records match work.
4 votes -
Delete Field Value Using Dedicated Syntax
We often have the need to delete/clear a field when importing. It would be great to have a dedicated syntax that we can map to indicate that the mapped field should be replaced with null.
E.g. if we map {DELETE} it would remove the value in the field in Salesforce that we are updating, leaving it blank.
This would allow blank fields to be ignored, whilst giving users a way to very intentionally delete a fields.
Two examples:
1) We have a file of donor data where invalid/incorrect email addresses and phone numbers have been flagged. We can therefore import…
3 votes -
Importing data to a field on a top level object ONLY if the field is blank and ignoring it if it's already populated
We have fields we'd like to import into a top-level object but only want them to import if the field in Salesforce is blank. If the field is already populated, then skip importing that field from Import Omatic.
3 votes -
Omatic user name populated as record owner
Populate the Omatic user name who is uploading the records to Salesforce into the associated records (opportunity, contact(s), and accounts.
3 votes -
Review specific fields that don't match the source destination
When importing we are overriding values in our destination system that we may not want to. For example, field X has a value of A in the source data and value of B in the destination - we'd like a way to review this prior to sending to the destination (similar to data differences) so we can make a choice if it's overridden or not. Ideally we'd be able to define these fields as they are unique to our organization and business rules.
This is similar to the following idea but seemed a little different. Other idea: https://omatic.uservoice.com/forums/950413-omatic-cloud/suggestions/48105404-option-to-get-user-input-when-incoming-data-doesn
3 votes -
Add a filter option for Classy campaigns.
Our organization has ALOT of published and unpublished campaigns in Classy. It would be wonderful to have the ability to search and select Classy campaigns by a filter vs. having to select from a very long list of "Campaign Names". It would also be great to have the option to search based on "Internal Campaign Name" since that is the field that is non-donor facing that we customize for our internal data mapping. For example, be able to filter Classy campaigns by their
campaign name or internal campaign name containing "renew", which for us, would allow us to create a…3 votes -
When copying a formula, copy all the setting of that formula (summary grid, matching settings, etc.)
2 votes -
Ability to Schedule Formula to do Refund Pulls in Classy to Update Opportunities in Salesforce.
We need the ability to pull Refunds from the Transactions Connector on a Scheduled basis. Currently, this would have to be a manual run because when a formula is scheduled it only pulls based on the created date not the Refunded date.
2 votes -
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 -
Increase number of search scenarios
Increase number of allowed search scenarios until Match Settings / Contact Match Search to more than five. Our use case is to match on ID (primary), then Name, Personal Email, Work Email, Alt Email, and Mailing Address.
1 voteHi Hannah - Thanks for your idea. One thing you may not be aware of is that with Salesforce if your object has more than 1 email address field then you can choose each of those email address fields when you create an Email or Name and Email match scenario. Thus instead of creating a match scenario for each of your email address fields in Salesforce you can create one match scenario and choose all of your email fields in that single match scenario. There is an implied OR between each of the email addresses when performing the search.
For example, suppose I have 3 email address fields (per your description) in Salesforce: Work Email, Personal Email and Alt Email. Suppose my incoming email address is steve@myorgname.org. I then add an Email match scenario and choose each of those email address fields in my match scenario. When Omatic Cloud attempts to match on email address the query…
-
Ability to Filter Out Test Emails from Salesforce Marketing Cloud
We are pushing Salesforce Marketing Cloud email data into Raiser's Edge actions through Omatic. We want the ability to test emails for any constituent in Salesforce Marketing Cloud, but not have those emails show on the constituent record they were tested for in Raiser's Edge. They didn't actually receive the email. There is not currently a way to filter out test emails. We learned the test email will have its own JobID and show an email in the TestEmailAddr field.
1 vote -
Ability to Filter Out Test Emails for Salesforce Marketing Cloud
We are pushing Salesforce Marketing Cloud email data into Raiser's Edge actions through Omatic. We want the ability to test emails for any constituent in Salesforce Marketing Cloud, but not have those emails show on the constituent record they were tested for in Raiser's Edge. They didn't actually receive the email. There is not currently a way to filter out test emails. We learned the test email will have its own JobID and show an email in the TestEmailAddr field.
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 -
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 -
1 vote
-
1 vote
-
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 -
Add Payout ID and Date to the API
Payout ID and Payout Date added to the API for reconciling between P2GL and OC integration. It's a critical information requirement.
0 votes -
Able to map Credit Card Brand from Stripe
requested the Brand name for credit card to be added to the connector.
0 votes
- Don't see your idea?