Information Needed

See more
See less

Connect says "not posted" despite transactions being present in Salesforce

  • Time
  • Show
Clear All
new posts

  • Connect says "not posted" despite transactions being present in Salesforce

    Hi there,

    I usually check weekly in Connect to see if there's any transactions that haven't posted to Salesforce. This week I found 10. However when I went to push them to SF, I found that those transactions (exact same order numbers) were already in Salesforce.

    If I push them again, I risk creating duplicates. But if I ignore the 'not posted' status, I risk losing transactions. So besides running every single order number into Salesforce to check what's where, I'm at a loss as to what to do. Is this a known bug? Do you know what might be causing it and how it can be fixed? I did notice that all the transactions took place on 12/9. Please advise.
    Some of the problematic transaction order numbers: 161296581511542436035 ; 161296594029462635237 ; 1612970542449440996 )

    Access granted, org ID = 00Dd0000000i8lD


  • #2
    This is duplicate of:
    Click & Pledge Support Department

    On Salesforce? Help us by rating our app: Click & Pledge Donor Management on AppExchange

    Join us @ the educational webinars:
    Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday:
    Are you on Salesforce? Join us at the Power of Us Hub: