Integration Errors: Salesforce

 

This feature is available on the following tiers: Enterprise, Advanced.

 

About

 This article contains the most common error messages that you can encounter with integrations to Salesforce.   If your error message is not in this article, please contact support@prontoforms.com for assistance.

 

Error Messages

Error

Solution

Required fields are missing: [Field Name]

This may appear on any Salesforce destination.  There are required fields on the Salesforce object that the data destination is not filling.  In order to create the record, required fields need to be filled.

You have either:

  • Not mapped a value from the form to this field
  • You've mapped a valuer, but with an incorrect DREL Reference
  • You've mapped a value, but that question in the form does not have an answer

You can review the list of standard fields on each object.  Choose the object you are trying to update, like "Account" from the left navigation and review the list of fields.  The "API Name" is the name that is revealed in the error message.  

If it is not on that list, it may be a custom field.  Find out which fields are required in the Object in Salesforce by talking to your Salesforce administrator.  

 

If fields are required in Salesforce, ensure that you do all of the below:

  1. Map a value from the form to that field using the data destination
  2. Make that question in the form required
 

No such column 'columname__c' on sobject of type Object__c

This may appear on any Salesforce destination.  It occurs when you have mapped data into custom fields that don't actually exist on the object in Salesforce.  The data destination is failing because it's trying to write a value to a field that doesn't exist.


To fix:
Confirm that the field name is typed correctly in the data destination, and confirm that it actually exists on the object you are writing to.

You can do this easily in the ProntoForms web portal by using the "Describe Salesforce Object" link directly above the area where you specify custom fields. 

Data Value Too Large

This may appear on any Salesforce destination.   Every field in Salesforce has a character limit, configured either by the field type or a custom limit.  The error occurs because the data from ProntoForms that you are trying to send to that field exceeds that character limit.  

To fix:
Either raise the character limit on that field in Salesforce, or use validation with a regular expression to limit the character length for the corresponding question in ProntoForms.

SOQL statements cannot be empty or null

This appears on Salesforce destinations where you have set up an Update Query to indicate when the destination should update an existing record.  The error occurs when your SOQL query resolves to an empty string.  Keep in mind that this query usually references the answer to a question using DREL. 

To fix:
First, check that you have correctly referenced the question and that your DREL expression is correct.

If the DREL expression is correct, the question likely has no answer.  The user may have skipped it, conditional logic may have forced the user to skip it (if it is hidden or ignored), or conditional logic may have cleared it.

If the question was simply missed by a user:

  • "Send for Edit" if the form allows it, and have a user fill the field
  • Modify your form definition so that it is "Required" in the future

If conditional logic cleared it or caused it to be skipped:

  • Modify your conditional logic and test to ensure that this question can never be skipped
{{FieldName}}: id value of incorrect type: {{FieldValue}}.

This type of an execution failure typically occurs when the dataType of the answer (FieldValue in this case) that was sent to the Salesforce Object destination does not match with the dataType of the Salesforce field it is writing to.

In this case,  FieldName is expecting an "id" value which is not compatible with the text value (FieldValue) that was sent to it.    This may also occur when sending a value to a Lookup that does not exist in the lookup. 

To fix:

  • "Send for Edit" if the form allows it, and have a user correct the submitted value
  • Or, modify the destination so it no longer sends the incorrect value to that field
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments