This article explains some of the most common issues you may have using Salesforce. Refer to Salesforce help documents for more detailed information.
The article provides information for the following User Roles:
Best Practices for Importing Leads and Contact Records
Importing/Updating Leads Via Import Tool: When importing/updating new leads to SharpSpring it is important to do the following:
- Be sure that Leads and Contacts are imported in separate CSV files. Under the Import New Leads In List As dropdown, select the correct lead type.
- The correct CRMID/External ID is being used in conjunction with lead or Contact. To obtain the correct 18 character CRMID you will need to do a Full export from Salesforce. For more information click here.
NOTE: In Salesforce, you can only do full exports manually once every 7 days (for weekly export) or 29 days (for monthly export).
You can find your Salesforce Error log using these steps.
Step One: On the top right side, click the Cloud.
Step Two: On the pop-up lower right, click Change Settings.
Step Three: On Salesforce Settings, click the Error Logs tab.
Step Four: To export error logs, on the top right click Options. Then in the drop-down, select Export Error Logs to CSV.
This CSV will contain the following columns:
- First Name
- Last Name
- CRM Lead ID
- CRM Contact ID
- Error Code
Most 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 / upsert records via the API using Dataloader, Informatica, Workbench, etc..
Resolution: 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 please make sure to select Always use CRM as soon as you re-assign the field.
This error happens if you have records with the same IDs coming from an external system. Unique fields are unique to a record and cannot be duplicated.
Resolution: 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 and 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.
FIELD_CUSTOM_VALIDATION_EXCEPTION 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 and you modify it so that the update does not reflect the filter criteria.
Resolution in Salesforce: 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 following these steps:
1. Go to Setup | Customize | Object | Fields.
2. Go to Scroll through your Standard and Custom Fields until you find a Lookup Field.
3. Click the Field Label and review the detail page to see if any filters exist.
4. Review the Filter Criteria to be sure your modifications adhere to it.
There's a problem with this state, even though it may appear correct. Please select a state from the list of valid states.: State/Province
Importing new or performing updates to existing records may result in data validation errors when State and Country picklists (S&CP) are enabled, if the address data contained in your file does not match the predefined state and country data.
Resolution in Salesforce:
- 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.
CANNOT_UPDATE_CONVERTED_LEAD: 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.
Salesforce Tips and Frequently Asked Questions
Industry Field: You will only be given one option from the drop down 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 dropdown 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 dropdown once the sync has taken place. The selected Salesforce industry dropdown options will also sync over to the SharpSpring industry field.
Converting a Lead to Contact within SharpSpring: If a Lead is synced between both systems and changed to a Contact within SharpSpring then the next time the sync runs a Contact record will be created in Salesforce. 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 in tact. 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 still existing Lead record in Salesforce that 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.
We recommend converting your lead to a contact within Salesforce to avoid duplicate records being created in Salesforce.
Company Name for Salesforce Contacts: Salesforce handles Contacts a little differently than SharpSpring. If you have Contacts and you want to sync over their Account Name, you will need to make a custom formula field in Salesforce that is a text field. The formula field will say _Account.Name_ and then save that field. When it appears in the Contact field mapping you'll need to make sure to set it to "Always use CRM" and you can map it to "Company Name".
Why doesn’t my Salesforce Picklist Sync? In order to successfully map to a picklist field it must be first created in Salesforce. With the Salesforce Sync enabled you will need to create a “New field” from the Assign to SharpSpring field mappings column. Once this field is created it will be available to edit under Third Party fields in our custom fields settings page. If you plan on mapping the same Third Party SharpSpring picklist to both Contacts and Leads the field settings and values must be identical in Salesforce for both Contacts and Leads.