Skip to main content
All CollectionsIntegrationsSalesforce
Connecting Salesforce & Juro - debugging errors
Connecting Salesforce & Juro - debugging errors

Bypass any errors you may encounter when using Juro's Salesforce integration

Sharen Gill avatar
Written by Sharen Gill
Updated over a week ago

Contents 🚀

  1. Introduction

  2. Common errors

  3. Seeing errors in Juro

  4. Seeing errors in Salesforce

Introduction 👋

It can be frustrating to receive a Salesforce error when you think everything is ready to go.

In this article, we look at how you can resolve some of the most common errors you may encounter when using Salesforce with Juro.

First, let's get a better idea of what these errors, and the individual fixes for them, are ⛑️

Common Errors 🌩️

Below, we've compiled a table of the most common errors our customers encounter when using our Salesforce integration.
​
Most of these can be resolved by following the guidance for the relevant error in the Resolution column.

Error

Resolution

Template was not published

  1. Publish the Juro template

  2. Retry the contract creation from Salesforce.

Mandatory field was left empty

  1. Go to Salesforce

  2. Fill the data into the affected field

  3. Retry the contract creation from Salesforce.

Incorrect field input for a choice field. (Juro will specify which field and what value it was expecting vs what it received from Salesforce)

  1. Crosscheck the Salesforce dropdown options for the single-select field against the choice field options within the Juro smartfield: these must be a character-for-character match, including any spacing and capitalisations

  2. Once updated, publish the template

  3. Retry the contract creation from Salesforce.

Salesforce credentials are inaccurate

This means that the username and/or password of the Admin member for the integration is now invalid. In Juro, you will need to disconnect the integration in all other workspaces and then:

  1. Go to AUTOMATIONS in the relevant workspace

  2. Select Integrations

  3. Select the Salesforce panel

  4. Disconnect and reconnect the integration using the updated valid credentials

  5. Once updated reconnect the other workspaces. Then, retry the contract creation from Salesforce

The contract did not update

Once contracts have been created, Salesforce continues to check the document while it's in progress. This error will show if:

  • a two-way sync is set on an incompatible field type

  • there is customisation/validation in place, and the criteria are no longer being met. To resolve this error:

  1. Adjust the sync type based on our compatibility matrix

  2. Adjust the fields so that the validation rules are met again

  3. Remove the validation or re-meet the validation rules to prevent this error from showing

Seeing errors in Juro 🚀

Organisation Admins in Juro can view errors in each workspace's integration log, and see a detailed description of why the error has occurred.
​
To do this:

1. Go to AUTOMATIONS in the relevant workspace and in the Integrations tab, click the Salesforce panel.

2. Click Open integration log, which will show the action that triggered the error.

Seeing errors in Salesforce 📉

Some errors generated from Salesforce will appear on the individual contract record.

However, most errors will show in the Integrations log of your AUTOMATIONS section.

💁‍♀️ As always, our Support Team is happy to help you with anything further if needed. Start a chat with us right here by clicking the Intercom button in the bottom-right-hand corner of this page.

Alternatively, you can email your query to support@juro.com 🚀

Did this answer your question?