Hi there,
In an audit of our C&P/Salesforce sync, we discovered 10 transactions from 2021 that had failed to post to Salesforce, and instead generated an "error" message in the Salesforce column.
We keep up to date with C&P updates so I don't believe that is the culprit for us (as a previous poster had mentioned), and none of the donations had been flagged as fraud (although the majority of them did appear to have something other than "yes" in the "CVV Match" field -- Yes/No, Yes/M, or No/No -- which was the only thing all transactions had in common as far as I could tell). The transactions spanned a variety of days & times between May-October 2021, were varying amounts from $5-$400, and a mix of recurring/one-time gifts. I manually clicked "post to Salesforce" on each of the transactions and that resolved the issue, but I'd love to know what caused it, if there's a way to prevent it, and/or how to catch it faster in future so we're not missing donor data in our Salesforce.
1 - Can you tell me why these 10 transactions errored out, instead of posting to Salesforce?
2 - Is there any way for us to turn on email notifications to admins when transactions error out like this, rather than having to rely on manually checking Connect periodically? (I noticed it's not possible to create a transaction report on the "Salesforce" column, as it doesn't appear as a column/field at all in the report creation screen).
Thanks so much.
Here are the impacted transactions --
24461-2105041549382462438
24461-2105202149230284709
24461-2106081315118478632
24461-2106151856121140903
24461-2106171004485256286
24461-210617100028175
24461-210713102411528
24461-2107251437468901211
24461-210728111454568
24461-211008151424140
Salesforce Org ID: 00Dd0000000i8lD
Access granted
In an audit of our C&P/Salesforce sync, we discovered 10 transactions from 2021 that had failed to post to Salesforce, and instead generated an "error" message in the Salesforce column.
We keep up to date with C&P updates so I don't believe that is the culprit for us (as a previous poster had mentioned), and none of the donations had been flagged as fraud (although the majority of them did appear to have something other than "yes" in the "CVV Match" field -- Yes/No, Yes/M, or No/No -- which was the only thing all transactions had in common as far as I could tell). The transactions spanned a variety of days & times between May-October 2021, were varying amounts from $5-$400, and a mix of recurring/one-time gifts. I manually clicked "post to Salesforce" on each of the transactions and that resolved the issue, but I'd love to know what caused it, if there's a way to prevent it, and/or how to catch it faster in future so we're not missing donor data in our Salesforce.
1 - Can you tell me why these 10 transactions errored out, instead of posting to Salesforce?
2 - Is there any way for us to turn on email notifications to admins when transactions error out like this, rather than having to rely on manually checking Connect periodically? (I noticed it's not possible to create a transaction report on the "Salesforce" column, as it doesn't appear as a column/field at all in the report creation screen).
Thanks so much.
Here are the impacted transactions --
24461-2105041549382462438
24461-2105202149230284709
24461-2106081315118478632
24461-2106151856121140903
24461-2106171004485256286
24461-210617100028175
24461-210713102411528
24461-2107251437468901211
24461-210728111454568
24461-211008151424140
Salesforce Org ID: 00Dd0000000i8lD
Access granted
Comment