Salesforce is massive. As such, you may come across errors while using the platform. This article details the more common issues you may have when using Salesforce.
The article provides information for the following user roles:
- Salesforce Resources
- Finding Error Logs
- Common Salesforce Errors
- Frequently Asked Questions
- Ready to Learn More?
This article provides basic information on daily API limits. For more information, contact your Salesforce administrator. Additionally, refer to the following external Salesforce documentation:
Finding Error Logs
To find your Salesforce error log, do the following:
When exported, this .CSV file will contain the following columns:
Common Salesforce Errors
Below are the most common SalesForce errors you may encounter with the Salesforce Sync enabled. We advise checking your error log on a regular basis. Reducing the amount of errors will speed up and reduce the amount API calls made to Salesforce.
You may encounter a Salesforce customer getting an INVALID_FIELD_FOR_INSERT_UPDATE: Attempting to update (as part of an upsert) parent field error when attempting to insert, update, or upsert records via the API using Dataloader, Informatica, Workbench, or other similar programs. This error can be resolved by un-assigning all of the parent fields you currently have mapped, and then selecting to retry the leads who are stuck in the error logs with this problem. If you still wish to have the parent fields afterwards, you can re-map them, but make sure to select Always use CRM as soon as you re-assign the field.
This error occurs if you have records with the same IDs coming from an external system. Unique fields are unique to a record and cannot be duplicated. This can happen when a lead or contact was imported with the wrong CRMID/External ID. To fix this, you will need to update the External ID with the correct CRMID from Salesforce via Import Tool. To obtain the correct 18-character CRMID, you will need to do a full export from Salesforce—not an activity report.
This error occurs when a lead or contact record has an invalid External ID/CRMID. This can also occur when a Salesforce contact is imported as a lead record in SharpSpring, or vice versa.
The error message FIELD_FILTER_VALIDATION_EXCEPTION, Value does not exist or does not match filter criteria occurs when there is a Look Up Field filter defined on an object that has been modified so that the update does not reflect the filter criteria. To fix this error, check to see if any filters are defined on the object, and make sure any modifications are adhering to the Filter Criteria. You can check if there are any filters on the object by doing the following:
Importing new or performing updates to existing records may result in data validation errors when state and country picklists are enabled if the address data contained in your file does not match the predefined state and country data. To resolve this, do the following:
- Set the default country to None in your state and country picklists setup section.
- Map both standard State and Country fields together.
The specified value in a relationship field is not valid, or data is not of the expected type.
Salesforce has a timeout limit for transactions based on CPU usage. If transactions consume too much CPU time, they will be changed to a long-running transaction.
A required argument is missing.
When you convert a lead to a contact, account, or opportunity, it cannot be updated as it does not exist anymore.
If a lead or contact has an error syncing into Salesforce, the lead or contact will then be disabled from syncing to Salesforce—even if the error is corrected. You have to select the option to retry the sync in the error logs of the CRM Sync Settings for it to enable the sync again for that lead or contact.
Frequently Asked Questions
Q: What are best practices for importing leads and contacts?
A: When importing/updating new leads to SharpSpring via the import tool, adhere to the following:
- Leads and contacts must be imported in separate .CSV files. When importing, under the Import New Leads In List As dropdown, select the correct lead type.
- Ensure the correct CRMID/External ID is being used in conjunction with leads or contacts. To obtain the correct 18-character CRMID, you will need to perform a full export from Salesforce. In Salesforce, you can only do full exports manually once every 7 days for weekly exports, or 29 days for monthly exports.
Q: Why am I seeing a discrepancy with the Date or Date/Time field?
A: Your SharpSpring company instance timezone is not set up to the same timezone as your synced Salesforce instance. When syncing, you will see the Salesforce time zone displayed next to the title of your Date or Date/Time field in SharpSpring.
Q: How does the Industry field work in each platform?
A: You will only be given one option from the drop-down list when mapping to the Salesforce Industry field. This is intended functionality so that the Salesforce Industry field can be mapped correctly to SharpSpring's Industry field. Salesforce uses a drop-down field, and SharpSpring uses a text entry field. Any text created in SharpSpring in the SharpSpring Industry field will be available in the Salesforce industry drop-down once the sync has taken place. The selected Salesforce Industry drop-down options will also sync over to the SharpSpring Industry field.
Q: What happens when I convert a lead to a contact within SharpSpring?
A: If a Lead is synced between both systems and changed to a Contact within SharpSpring, a contact record will be created in Salesforce the next time the sync runs. All the mapped field information in the record in SharpSpring will be synced to the new contact record in Salesforce. Since leads and contacts are categorized differently in Salesforce, the original Lead record in Salesforce will remain intact. If changes are made in SharpSpring to this record, then the changes will only sync to the contact record in Salesforce. If a change is made to the contact record in Salesforce, then it will update the record in SharpSpring.
Keep in mind both the Salesforce lead record and contact record are technically still connected with the contact record in SharpSpring. This means that if a change is detected in the existing lead record in Salesforce, it will sync all of its information back to the record in SharpSpring and change the SharpSpring lead status back to a lead. Changes in SharpSpring to the record from that point on would sync to the lead record in Salesforce. Converting your lead to a contact within Salesforce avoids duplicate records being created in Salesforce.