No announcement yet.

FaaS Donation not posting to Salesforce

  • Time
  • Show
Clear All
new posts

  • FaaS Donation not posting to Salesforce

    Hello all,

    Hopefully, you can help me with this. I'm building a donation page using FaaS, and while our Test transactions are going through without a problem and posting to Salesforce, when we switch to production and put in a real credit card, the transaction goes through just fine, but doesn't show up in Salesforce, even though we received the receipt from Click & Pledge.

    Can you please take a look at the form?
    Here are the links:

    The production form:

    The test form:

    Also, please let me know if there is any additional information you need to help us troubleshoot.
    Thanks so much!

  • #2
    I just saw something in the C&P Data Tab in Salesforce that might be useful. In the message section it says the following:
    Update failed. First exception on row 0 with id 003U0000004xXWmIAM; first error: CANNOT_INSERT_UPDATE_ACTIVATE_ENTITY, npo02.Households: execution of AfterUpdate

    caused by: System.DmlException: Delete failed. First exception on row 0; first error: ENTITY_IS_DELETED, entity is deleted: []

    : []
    I figure that this might have something to do with it. What can I do to fix this?


    • #3
      Good day!

      What version of the PaaS is currently installed in your Salesforce instance?

      The error is quite descriptive and is telling us what is going on. A trigger on Household is failing & that is an issue with the Nonprofit Starter Pack.

      Please go to Settings > Installed Packages and let me know what version of our application you have installed.

      Latest version was released this morning and may be installed from either the appExchange or the following post:

      Click & Pledge Support Department

      Join us @ the educational webinars:
      Live Support- read more:


      • #4
        but, we are not using PaaS, we are using FaaS. Should I try installing the new PaaS even though I'm using FaaS.
        Right now, we have version 3.150 of the Click & Pledge Donor Management.

        Here is a screenshot of our installed packages.
        Click image for larger version

Name:	installed packages.jpg
Views:	1
Size:	14.7 KB
ID:	15041


        Please let me know if I need to upgrade.



        • #5
          Good day!

          Salesforce PaaS platform is the app you are using and you are in version 3.x which is an old release and no longer supported.

          Please see the following post:

          Please contact [email protected] immediately and request an upgrade. You will be asked to set up a user with admin rights so we can upgrade your account. It will be handled by our team and we will notify you once completed.

          Once we have upgraded your account we can review the error if it still persists.
          Click & Pledge Support Department

          Join us @ the educational webinars:
          Live Support- read more:


          • #6
            Excellent, I will send them an email requesting a migration and let you know if that resolves the problem. Thank you!


            • #7
              Unfortunately, we upgraded to Version Number 4.27 and the error is still persisting.
              Can you please help us out?


              • #8
                Good day!

                One of our support engineers will be calling you and help with the issue. We have to see the exact reason for the error and what is causing it.

                Please also note that the latest version is 4.32

                Please contact [email protected] and arrange for a screen sharing session.
                Click & Pledge Support Department

                Join us @ the educational webinars:
                Live Support- read more:


                • #9
                  Thanks so much for the help. The problem is resolved.
                  In case anyone runs into a similar problem in the future, the problem was that we made so many test transactions that Click&Pledge blacklisted my email and IP.
                  I talked with support and they cleared it up.