Index:
Airtable Errors:
2. “Unknown field name: “{{Field}}”
3. “Field ‘{{Field}}’ cannot accept a value because the field is computed”
Salesforce Errors:
2. “Cannot parse date value ‘’ for field {{Field}}”
3. “No such column on object of type Lead”
4. “Required fields are missing: [Field]”
6. “You’re creating a duplicate record. We recommend you use an existing record instead.”
7. “Use one of these records?”
8. “bad value for restricted picklist field: {{Field}}”
9. ”{{Field}} is expected to be select”
10. ”{{Field}}: data value too large”
11. “We can’t save this record because {{Flow}} process failed.”
Google Sheets Errors:
Notion Errors
.png){kind=small}
Airtable: “Internal Server Error”
• Explanation: This error indicates that the connection between Form Connector and Airtable might have been deleted from your Airtable account.
• Solution: Turn off all Airtable connectors, delete Airtable as a destination in Form Connector, and connect it again.
Airtable: “Unknown field name: ”
• Explanation: Airtable cannot recognize the specified field name because it may have been deleted or its ID changed.
• Solution: Update the field mapping in Form Connector to match the current Airtable configuration.
Airtable: “Field ‘{{Field}}’ cannot accept a value because the field is computed”
• Explanation: Computed fields in Airtable, such as formula fields, cannot accept external data submissions.
• Solution: Remove the computed field from your Form Connector mapping to avoid sending data to it.
To review all supported and not supported Airtable fields, please refer to this guide.
Salesforce: “Failed to refresh token"
• Explanation: This error suggests that the token used by Form Connector to connect with Salesforce has expired or is invalid.
• Solution: Turn off all Salesforce connectors, delete Salesforce as a destination in Form Connector, and connect it again.
Salesforce: “Cannot parse date value ‘<true>’ for field {{Field}}”
• Explanation: The data submitted for a date field does not match Salesforce’s required format.
• Solution: Confirm that the data format in the form submission aligns with Salesforce’s expected date format for the field.
Salesforce: “No such column on object of type Lead”
• Explanation: Salesforce cannot find the specified field in the Lead object.
• Solution: Verify that the field exists in Salesforce and is correctly mapped in Form Connector.
Salesforce: “Required fields are missing: [Field]”
• Explanation: One or more required fields in Salesforce are missing values in the form submission. This error can also occur if a skip-if formula in the form bypasses a required field, leaving it empty.
• Solution: Ensure that all required fields are mapped in Form Connector and are populated with data in the form submission. If a skip-if formula is used, verify that it doesn’t prevent required fields from being filled when necessary.
Salesforce: “{{Field}} is required”
• Explanation: This error indicates that a required field was submitted without a value. When a field is required in Salesforce, simply including the field in the form submission isn’t enough—Salesforce expects it to have data. If the form submission includes the field but leaves it empty, Salesforce will treat this as if the required field is missing and return the ”{{field}} is required” error.
• Solution: To avoid this, you can implement validation in the form itself to ensure that required fields contain data before submission. This way, users are prompted to fill in all required fields, reducing the chances of blank submissions.
Salesforce: “You’re creating a duplicate record. We recommend you use an existing record instead.”
• Explanation: Salesforce’s duplicate management rules have detected a record that appears similar to the current submission.
• Solution: Adjust the submission data to avoid duplicates or review Salesforce’s duplicate rules.
Salesforce: “Use one of these records?”
• Explanation: Salesforce has detected potential duplicate records and is suggesting existing records as matches to prevent creating a duplicate.
• Solution: This duplicate detection and management occur within Salesforce, based on its duplicate rules. Currently, Form Connector only supports creating new items, not updating existing ones. To handle duplicates, review and adjust Salesforce’s duplicate management rules.
Salesforce: “bad value for restricted picklist field: {{Field}}”
• Explanation: The submitted value does not match Salesforce’s allowed values for a picklist field.
• Solution: Verify that the form data aligns with Salesforce’s predefined picklist options for this field.
Salesforce: “{{Field}} is expected to be select”
• Explanation: Salesforce expects a specific selection (e.g., checkbox or picklist) that wasn’t provided in the submission.
• Solution: Check that the submission meets Salesforce’s expected field type or selection criteria.
Salesforce: “{{Field}}: data value too large”
• Explanation: The submitted value exceeds the character limit for this field in Salesforce.
• Solution: Ensure the data fits within the maximum allowed characters for the field. Limit can be set on Salesforce.
Salesforce: “We can’t save this record because {{Flow}} process failed.”
• Explanation: A Salesforce automation or process builder rule failed due to an object type mismatch.
• Solution: Review the mentioned automation and check any trigger or workflow you have set in salesforce related to the object mentioned. Adjust the submission data to match Salesforce’s required object type.
.png){kind=small}
Google Sheets: “Internal Server Error”
• Explanation: The connection between Form Connector and Google Sheets was removed.
• Solution: Turn off all Google Sheets connectors, delete Google Sheets as a destination in Form Connector, and connect it again.
Notion: “Internal Server Error”
• Explanation: This error indicates that the connection between Form Connector and Notion was deleted.
• Solution: Turn off all Notion connectors, delete Notion as a destination in Form Connector, and connect it again.
Notion: “{{Field}} is not a property that exists.”
• Explanation: This means that the specified field was deleted or renamed in Notion.
• Solution: Update the field mapping in Form Connector to match the current properties in your Notion database.
Thank you for using this guide to troubleshoot your submission errors. I hope it helps you find quick solutions!
If you still have questions or need more assistance, feel free to reach out—I’ll be happy to help you resolve any issues.
