Resolving Common Lead Conversion Errors in Salesforce

Required Fields Error

The error System.DmlException: Insert failed with the detail Missing Required Field (REQUIRED_FIELD_MISSING) occurs if a required field on an Account, Contact, Opportunity, or an associated Task is blank during conversion.

• For Accounts, Contacts, or Opportunities: This happens when a value isn't mapped to a required field. An administrator must create a lead field and map it to the corresponding required field on the destination object. More information about this can be found in
  Mapping Custom Lead Fields.

• For Tasks: If a task is the issue, its ID will be in the error message. To fix this, ensure that required fields are populated on all tasks associated with the lead.

• Workaround: You can set a default value for the required field in the Lead Settings or deselect Require Validation for Converted Leads.

Lookup Field Filter Error 

The error FIELD_FILTER_VALIDATION_EXCEPTION occurs if a value being mapped doesn't meet the criteria of a lookup field filter or if the mapped fields have different data types. To fix this, make the lookup filter "Optional" instead of "Required" or adjust its logic. For detailed steps, refer to Received error: FIELD_FILTER_VALIDATION_EXCEPTION, Value does not exist or does not match filter criteria.

Pending Time-Based Workflow Actions Error

The error "Unable to convert lead that is in use by workflow" occurs due to a pending time-based action on the lead. To fix this, find and delete the pending action to proceed. For detailed steps, refer to  Unable to convert Lead that is in use by workflow.

Custom Validation Errors

Validation rules for Leads, Accounts, Contacts, and Opportunities are enforced during conversion only if the Require Validation for Converted Leads setting is enabled. These errors appear in bold red letters below the Converted Status picklist. For more details, see Validation rule not firing when converting Leads.

Custom Apex Errors

These errors name the problematic Apex trigger and must be examined by a developer for troubleshooting.

Invalid Cross Reference Key Error

To fix this error, grant Edit access to the lead record or check if the record is locked in an approval process.

Archived Activities Error
The error “There was an error converting the lead. Please try again. If the problem persists, please contact your administrator” can be fixed by unarchiving all the activities (events and tasks) related to the impacted lead. Fetch them by executing the SOQL query with 'Include archived/deleted records' checkbox - SELECT Id, IsArchived, EndDate FROM Event WHERE Id IN (Select EventId from EventRelation where RelationId = '<lead-id>') and isArchived=true

Dependency Exists Error

The error DEPENDENCY_EXISTS You cannot bulk insert or update relations for a recurrence together with its occurrences for object EventRelation: [Event] can have 2 causes:

• Archived events and tasks.

• Events with occurrences and recurrences that have GroupEventType=3. Events that have GroupEventType=3 have corrupted data, causing errors. 

To fix the error, unarchive all the activities (events and tasks) related to the impacted lead. Fetch them by executing the SOQL query with 'Include archived/deleted records' checkbox - SELECT Id, IsArchived, EndDate FROM Event WHERE Id IN (Select EventId from EventRelation where RelationId = '<lead-id>') and isArchived=true.

If the error persists, unlink all the events related to the impacted lead record. Then, perform lead convert and relink the events to the converted contact, account, or opportunity.