Diana K.
My feedback
19 results found
-
2 votes
-
247 votes
An error occurred while saving the comment -
3 votes
-
3 votes
-
4 votes
-
8 votes
-
11 votes
-
2 votes
-
6 votes
-
14 votes
-
7 votes
-
6 votes
-
13 votes
-
7 votes
-
1 vote
-
2 votes
-
9 votes
-
1 vote
-
1 vote
I agree with the previous contributors. This is a mission-critical enhancement.
As new Omatic Cloud customers, our team was surprised that a shared transformation repository or dictionary type feature was not available out of the box. In Import-O-Matic, we maintained a well-organized dictionary structure that allowed us to manage, test and reuse mapping logic efficiently across multiple imports.
We maintain over 200 Appeals and Packages (Direct Response, Event, Corporate, and General Giving). Recreating and maintaining similar transformation logic across multiple formulas in Omatic Cloud is time-consuming and increases the risk of inconsistencies or simple data mapping errors between transformations.
A central repository that could be applied across multiple formulas would significantly improve efficiency, consistency, and governance.
We would also welcome a transformation testing feature similar to what was available in Import-O-Matic. Currently, validating a transformation often depends on waiting for live transactions to flow through the system. The ability to test transformations against a sample or dummy record before deployment would improve quality control, and reduce risk and gift processing exceptions.
For organizations managing large fundraising and gift-processing portfolios, both features would provide substantial operational benefits and help streamline ongoing maintenance.
Thank you for your attention to this request. We appreciate the hard work and innovation that your development team continues to put into Omatic Cloud.
We're looking forward to seeing this come to fruition, hopefully before the holiday giving season 😉. Fingers crossed!