General Discussion

 View Only

This Week in Support: Solving a common ticket about Salesforce destination duplicate key errors

  • 1.  This Week in Support: Solving a common ticket about Salesforce destination duplicate key errors

    Posted 10-13-2022 08:00
    Edited by Pat Cooney 02-06-2024 11:50

    In ProntoForms Support, we see customers raise tickets about “Duplicate Key” errors like in the below screenshot when a Salesforce destination runs. 


    Our Salesforce destination documentation describes that this can happen when a Salesforce Case, Contact, Lead, or Account object field is filled in while also using the same field in the custom Salesforce fields section. In the screenshot below you can see that the Description is filled in as a case field as well as a field in the Case object to update. 


    To overcome this issue, you should remove the duplicate mapping from the custom Salesforce field section so that the integration can correctly update the case field with the correct information. In the above example, this would mean removing the key value pair of Description and %a[Branch] so that the Description case field is correctly updated.  


    #TechTalkSupport
    ------------------------------
    Jesse Collier
    Senior Technical Engineer
    ProntoForms
    ------------------------------



Reminder: Content posted to our Community is public content.  Please be careful not to post Intellectual Property that you do not have permission to share.  For more information please refer to our Terms Of Use