Omatic Cloud
12 results found
-
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 -
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 -
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 -
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 -
Import from One system of Record into the Same System of Record
We would like to create a formula that will take a Salesforce (SF) report and update the data in SF automatically. The formula set up page does not have the option "Salesforce Production to Salesforce Production". The only options are "Salesforce Production to Flat file" and "Salesforce production to Salesforce Sandbox"
Reference case 00094322
2 votes -
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 -
Able to map Credit Card Brand from Stripe
requested the Brand name for credit card to be added to the connector.
0 votes -
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 -
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 -
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 -
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 -
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
- Don't see your idea?