Announcement

Collapse

Information Needed

See more
See less

transaction is posted, but keeps creating a new temp contact - and has no GUID

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

  • transaction is posted, but keeps creating a new temp contact - and has no GUID

    Hi there! I have a transaction that originated from a temporary contact, which I processed and added to an existing contact. The transaction keeps triggering a workflow rule that sends me a notification, and when I look at the transaction data (a0qo0000001koC9AAI), it shows all zeros in the gateway transaction number. I can't see what about the transaction needs to be fixed to stop this from happening.

    When I do a search in my org for the contact's first name (Alois), I see in the section listing the C&P Transactions, there are two transactions for this contact that show a Vault GUID, and the weird transaction in question has no GUID, in case this is related to the issue.

    I've granted access to our org, ID 00Do0000000I2hr, if someone could check into this. Thanks so much!!



  • #2
    Hi again - the transaction has gone back to being a temporary contact now, which I haven't processed yet, since hopefully you can see what's happening better from the start. It is Transaction No. TC-0405. Thanks!

    Comment


    • #3
      Good day!

      We do not have access to your account. Please grant us access so we can review.

      Click image for larger version

Name:	Login.jpg
Views:	26
Size:	31.6 KB
ID:	22665
      Regards,
      Click & Pledge Support Department

      Join us @ the educational webinars: https://clickandpledge.com/webinars/
      Live Support- read more: https://support.clickandpledge.com/s/article/general-information-live-support/

      Comment


      • #4
        Whoops! Very sorry I forgot that part. Just granted 30 day access. Thank you so much!

        Comment


        • #5
          Good day!

          We have reviewed the error cases and see the following errors: Click image for larger version

Name:	CnP-Data.jpg
Views:	25
Size:	82.4 KB
ID:	22692




          The 4 errors are for event registrations and based on the review of the posted data the registrant that was used for registration has been deleted. Please see the posted data: Click image for larger version

Name:	RegistrantID.jpg
Views:	27
Size:	37.3 KB
ID:	22693




          The ID associated with the Registrant is no longer in your system. It appears that this registrant record has been deleted.

          Have you deleted any registrations manually?
          Regards,
          Click & Pledge Support Department

          Join us @ the educational webinars: https://clickandpledge.com/webinars/
          Live Support- read more: https://support.clickandpledge.com/s/article/general-information-live-support/

          Comment


          • #6
            Hi! That actually was a separate issue. Yesterday I noticed several duplicate transactions for that contact - see attached screenshot. While I was in the process of looking through the support forum in order to see what I should fix, I got several error reports from Click & Pledge notifying me of errors when posting four transactions related to this contact, and apparently they were then automatically deleted - I did not delete any transactions myself. The contact had tried a event registration and his credit card was declined, and then he tried again and it was successful. It looks like the transactions related to the declined transactions are all deleted now, and the authorized one preserved.

            The issue I was originally posting about was that a temporary contact for Alois Heinemann does not have a payment gateway number (it's all zeros) and when I posted it, it would continue to generate a workfulow rule that gets triggered when a declined credit card transaction is posted. Then it would eventually go back to being a temporary contact. This also arose from a declined credit card transaction, but via PaidMembershipsPro.

            I am happy to go ahead and delete this temp contact and just wait to see if the problem arises again in the future. but I just wanted to report it in case there is any bug behind the scenes that should be identified. I've left the temp contact in so you can look at it -TC-0405. Thanks!

            Here's the screenshot of the weird duplicate transactions for Joel G. that then got deleted.


            Comment


            • #7
              Good day!

              Would you please post the image as JPG. The forum platform does not show PNG files in full size and the size that is being shown is not legible.
              Regards,
              Click & Pledge Support Department

              Join us @ the educational webinars: https://clickandpledge.com/webinars/
              Live Support- read more: https://support.clickandpledge.com/s/article/general-information-live-support/

              Comment


              • #8
                Thanks - will post JPGs from now on :-) It looks tiny to me and I can't see how to change the sizing...

                Comment


                • #9
                  Hi - I've gone ahead and processed the temporary contact in question, and it appears to have posted successfully. If it mysteriously comes back in as a temp contact I will post again; otherwise this can be considered resolved. Thanks!

                  Comment


                  • #10
                    Good day!

                    The issue is the Maintenance. If there is an error it will be processed again.

                    Do you have an order number for this contact's transaction? We need to review the C&P Data and see if an error has occurred.

                    Maintenance process all C&P Data that has resulted in Error. Do you have the order number?
                    Regards,
                    Click & Pledge Support Department

                    Join us @ the educational webinars: https://clickandpledge.com/webinars/
                    Live Support- read more: https://support.clickandpledge.com/s/article/general-information-live-support/

                    Comment


                    • #11
                      Thanks - it's order

                      Comment


                      • #12
                        Good day!

                        This order is in the Temp:

                        Click image for larger version

Name:	2016-03-29_10-23-53.jpg
Views:	26
Size:	96.0 KB
ID:	22850


                        Is it OK to merge this record with the one already in the system?

                        Click image for larger version

Name:	2016-03-29_10-26-51.jpg
Views:	25
Size:	104.1 KB
ID:	22851

                        We want to make sure there are no errors when you are merging them. It is in the Temp at this time and we just want to settle it and see what happens to the C&P Data.
                        Regards,
                        Click & Pledge Support Department

                        Join us @ the educational webinars: https://clickandpledge.com/webinars/
                        Live Support- read more: https://support.clickandpledge.com/s/article/general-information-live-support/

                        Comment


                        • #13
                          Ah, yes, exactly - this is what keeps happening with this transaction. I did merge it with that existing contact, and then it goes back to a Temp Contact. So if you can try merging it that would be great, thanks!

                          Comment


                          • #14
                            Good day!

                            Strange behavior indeed. We have resolved it in your instance.

                            Please let us know if we can be of any further assistance.
                            Regards,
                            Click & Pledge Support Department

                            Join us @ the educational webinars: https://clickandpledge.com/webinars/
                            Live Support- read more: https://support.clickandpledge.com/s/article/general-information-live-support/

                            Comment


                            • #15
                              Phew! Thank you. Much appreciated.

                              Comment

                              Working...
                              X