Omatic Cloud
2 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
- Don't see your idea?