Announcement

Collapse
No announcement yet.

Transaction not showing up in Connect

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Transaction not showing up in Connect

    Hello,

    I'm seeing a transaction in TransCentral but it's not showing up in Connect or integrating with our Salesforce. Is this a TransCentral issue or can you see if it's a connectivity issue?
    ,
    Ref ID: 50733-1811301648478790120

    Thanks!

    Lauren

  • #2

    Good day @laurenzastrow

    We see the above order number in the Connect. Please see:

    Click image for larger version

Name:	connect transaction.jpg
Views:	1
Size:	149.2 KB
ID:	43661

    Regarding the data posting to Salesforce, we encounter the following error while posting the data: npsp:Too many SOQL queries: 101

    The above error is related to NPSP. NPSP is reaching 100 SOQL queries and you will need to review the NPSP Settings in order to resolve the issue.
    Regards,
    Click & Pledge Support Department

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

    Join us @ the educational webinars: https://clickandpledge.com/webinars/
    Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
    Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

    Comment


    • #3
      Good afternoon. I too have tried to repost this transaction on behalf of the client and I get an email with the error: "Salesforce Connection Failure
      Sorry but we are unable to establish connection with your Salesforce instance. Your application is out-of-date and needs to be updated to the latest release prior to establishing connection." I just checked and we have the most up to date versions of the class library and PAAS app. Can you help us solve why we can't post this transaction and why the error message is that we are out of date when that is not the case. I've granted access to the SF Org ID:00DF00000008F4u. The previous post above states that an error was given from NPSP. How did the user recieve that error? I did not recieve that error. I checked NPSP Settings' error log in the org and didn't see anything from that time frame? Thanks for your help.

      Comment


      • #4
        Good day @chad@percolatorconsulting.com

        Given you are up to date, please disregard the above message. I have asked our team to remove your Organization from a list of notification. Regarding the NPSP error, you won't receive that message nor NPSP will record in the logs since the data didn't post to Salesforce and return the error to C&P.
        Regards,
        Click & Pledge Support Department

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

        Join us @ the educational webinars: https://clickandpledge.com/webinars/
        Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
        Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

        Comment


        • #5
          Our original issue still persists so any direction you can offer us for a solution will be appreciated. To provide more context for the issue: This transaction was entered from Salesforce Virtual Terminal. No error message was given upon submission, but the transaction did not show up in Salesforce, and yet it is present in Connect and the TransCentral. We've attempted many times to repost the transaction from Connect, but nothing is created in Salesforce. The Status of the transaction in Connect shows "Error". One thing I noted in connect is that there isn't an email address. I would assume this would add the transaction to temporary contacts in SF, but that is not the case. I'm wondering if the lack of email leads to the query taking too long. If that might be the solution we can connect privately to get that email filled in. Or you can access the contact in the SF org and get the email. Otherwise, I have no other leads to follow so would appreciate any other suggestions. At this point if you are able to manually recreate the transaction in SF with all of the appropriate C&P related records, that would suffice. thanks for helping with this!

          Comment


          • #6
            Chad, as stated above NPSP is reaching the limit of queries when we are trying to insert the data. As you can see below when we tried to insert the above transaction manually into your instance we see the following in the debug logs which clearly states that the NPSP is reaching 100 SOQL queries.

            Click image for larger version

Name:	Limit usage1.jpg
Views:	1
Size:	91.3 KB
ID:	43738

            Click image for larger version

Name:	Limit usage2.jpg
Views:	1
Size:	100.0 KB
ID:	43739

            It is not at all related to the email since the contact is already exist in your instance, here is the ContactID: 0031Y00005NNUjNQAX
            Regards,
            Click & Pledge Support Department

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

            Join us @ the educational webinars: https://clickandpledge.com/webinars/
            Live Support available Join between 3:00 - 3:30 p.m. ET Monday - Thursday: https://clickandpledge.com/webinars/
            Are you on Salesforce? Join us at the Power of Us Hub: https://powerofus.force.com/0F980000000CjpC

            Comment


            • #7
              I very much appreciate this detail. We can use this to look deeper into the situation. I will respond if any other questions come up as a result.

              Comment


              • #8
                We were able to solve the problem and I'd like to pass on the information to your developers in case it can add to functionality in the future: The email field on the contact was blank and the email field on the transaction in Connect was blank. Our matching criteria in C&P settings is first,last,any email. We added a junk email address to the contact record in SF, then reposted from Connect, and the transaction successfully made it to the contact. Our guess is that since email is needed for a match according to the criteria, but was missing on both sides, C&P just kept looking for a match until it hit the limit because it wasn't set up to deal with nulls on both sides. Ideally in this situation we would either want to see the transaction end up in Temporary Contacts, since first and last matched, but email didn't because both were blank, OR we'd like to see the donation go to the right contact since this contact was the only one with this first and last name. So some added logic to C&P code might help like "if email is blank on both ends AND other criteria matches AND there is only one match, THEN add to contact OTHERWISE add to temp contact. Thanks for your help, you can consider this closed.

                Comment

                Working...
                X