- Error #1: Please check your Salesforce configuration or try again later
- Error #2: Missing required fields
- Error #3: Missing Data on a newly created account
You may not have permission to create new accounts or update existing accounts.
You may not have permission to add or edit certain fields.
You may not have permission to update accounts that you do not own.
Your Salesforce may be configured to prevent duplicate accounts against a certain field such as registered company number.
One of your required account fields may be a picklist field (multiple choice dropdown) rather a free text field. We are currently unable to map to picklist fields.
Error #1: Please check your Salesforce configuration or try again later
Our Salesforce Connector must respect your individual access rights on Salesforce. Any of the following could prevent you from creating or updating an account:
Try manually creating the same account on the Salesforce website using the same company information that we attempted to enter on your behalf. You will be told what is preventing Salesforce from creating or updating the account and your Salesforce administrator will be able to change these settings for you if appropriate.
Error #2: Missing required fields
This error will likely be shown we you are configuring your Salesforce Connector. This error means that you have required fields in your: account, contact or lead fields. As a result, your salesforce rule dictates that the field cannot be null and the the moment it has no default value set.
The required fields will be clearly highlighted in red. If there are no required fields highlighted but you are still seeing this error get in touch with us via email@example.com or through the Intercom chat.
Error #3: Missing Data on a newly created account
Many organisations add new Salesforce fields over time but may not remove disused ones. For example, you might now use field called 'Billing Postcode' but 'Billing Postal Code' could still be present in the account object. Check your field mappings carefully to ensure you are not sending data to a disused field with a similar name to the fields you now use.