Allow records causing exceptions to be edited before resending to destination
Occasionally a record will be rejected by the destination app because the data violates some data formatting rule in that app. The main example in my setup is my Mailchimp lists do not allow non-US Zip codes, so when Omatic tries to create or update a subscriber whose Altru Zip is from a different country, it throws an exception. The only way to get the subscriber into Mailchimp is to either add them manually or temporarily remove the Zip from Altru and force the record to go through the Omatic formula again. It would save a lot of time if records already in the Omatic formula could be edited so I could simply remove the 'unacceptable' data there and then resend the record(s) to the destination.
Bill Carey
shared this idea
The ability to perform inline editing within the Destination Exceptions bucket is now available in Omatic Cloud!
-
Christina Hoffecker
commented
This is a critically needed feature since right now, the only way to manage a destination exception when records are set to route to ready is to 1) make a change in the record routing rules 2) reprocess the records 3) correct the data 4) send the data 5) change the record routing rules back to the original settings (send to renxt).
This would save a lot of time and prevent a destination exception loop.
-
Cody Murray
commented
What also might help this is allowing in-line editing for destination exceptions and allowing to send.