Announcement

Collapse
No announcement yet.

Back-to-back Transactions Creating Duplicate Contacts in Salesforce

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

  • CnP.Support.AM
    replied
    Good day @Perc-BRC

    Please note that you will need to delay the second transaction for 30 seconds to hit the API. Regarding your other questions, as of now, it is not possible to combine one time and recurring transaction.

    Leave a comment:


  • Perc-BRC
    replied
    Hi,

    Any update on this? Here are some other questions I am hoping to get answered:
    1. How much time should be between transactions to ensure we don't get dupes?
    2. Is there any way to have one transaction that combines a one-time donation and a recurring donation?
    3. If not, is there any way to have one POST that includes a one-time transaction and a recurring transaction in such a way we don't get dupes in Salesforce?

    Thanks.

    Leave a comment:


  • Perc-BRC
    replied
    PS I am using the Salesforce class library, but my posts in that forum went unanswered.

    Leave a comment:


  • Perc-BRC
    replied
    Hi, I built the form. Can you point me in the direction of documentation that shows how to have a single transaction with some items that recur automatically every year and some that do not?

    Thanks.

    Leave a comment:


  • CnP.LiveSupport.AB
    replied
    Sure. Our API does handle multiple items on a single transaction. The URL you provided as the source for these transactions is a custom form. Do you know who built it for you? Someone would need to edit the code of the form to submit multiple items.

    Leave a comment:


  • Perc-BRC
    replied
    This isn't double submission, these are two transactions we are processing back to back. One of them is recurring and one of them is a one-time donation.

    Is there a way to ensure that two back-to-back transactions aren't handled simultaneously?

    If not, is there a way to have a single transaction incorporate a one-time donation and a recurring donation?

    Leave a comment:


  • CnP.Support.AM
    replied
    Good day @Perc-BRC

    It is Salesforce that how it works. All you can do is validate the submit button of your donation page to avoid double submission.

    Leave a comment:


  • Perc-BRC
    replied
    Thanks for the diagnosis! Do you have any advice on how to handle this so we don't get duplicates?

    Leave a comment:


  • CnP.Support.AM
    replied
    Good day @Perc-BRC

    We reviewed and found that the two transactions which you are referring to have processed with the same info with no difference of a second and in this case in Salesforce it will create duplicate contact. Please note that in Salesforce there is a queueable process, each process checking back to back for the existing contact which leads the duplicate contact creation.

    Leave a comment:


  • Perc-BRC
    replied

    Leave a comment:


  • CnP.Support.AM
    replied
    Good day @Perc-BRC

    Would you please share the link URL of the page from where the above transactions processed?

    Leave a comment:


  • Perc-BRC
    replied
    Hello,

    I granted access to our org. Let me know if you need the org id and what email I can send that to.

    The two order numbers are:
    31804-2011021710598611111
    31804-2011021710588291111

    Thanks,
    Drew

    Leave a comment:


  • CnP.Support.AM
    replied
    Good day @Perc-BRC

    Would you please grant us login access to your Salesforce instance and share the order numbers which processed back to back and created duplicate contacts so that we can review it?

    Looking forward to hearing back from you.

    Leave a comment:


  • Back-to-back Transactions Creating Duplicate Contacts in Salesforce

    We are using the API to make make two Credit Card transactions back to back (we do this because only one of them is recurring) and using the "Full Matching" setting in Salesforce.

    I've noticed that it will create duplicate Contacts in Salesforce, one for each Transaction, rather than creating a Contact for the first Transaction and then matching to that Contact with the second Transaction.

    Is this because both Transactions are processing in Salesforce simultaneously? Is there anything we can do to prevent that?
Working...
X