Print this page

Error when converting a lead

Knowledge Article Number 000212944
Description There are several reasons why an error message may be presented to the user during lead conversion. Get the common reasons why errors are presented during lead conversion and how to correct these errors.
Resolution

Custom Validation Error Account, Contact, Opportunity, Lead Validation Rule

Validation rules are enforce on lead conversion for the Lead, Account, Contact, Opportunity objects. This is only true if the "Require Validation for Converted Leads" setting is checked. Otherwise, only Lead validation rules are enforced on lead conversion.

Custom validation errors will display as bold red letters below the Converted Status picklist.

FIELD_FILTER_VALIDATION_EXCEPTION, Value does not exist or does not match filter criteria

This error message, occurs when there is a Lookup Field filter defined on an Object and you modify it so that the update doesn't reflect the filter criteria. 

Click on the link given below to get the steps to resolve this issue: 

Received error: FIELD_FILTER_VALIDATION_EXCEPTION, Value does not exist or does not match filter criteria


This issue can also occur due to a lookup filter on one of lookup field on the target object/s upon lead conversion (Account, Opportunity and Contact). 

Error: "System.DmlException: Insert failed. First exception on row 0; first error: FIELD_FILTER_VALIDATION_EXCEPTION, Value does not exist or does not match filter criteria."

Make the lookup filter as 'Optional' instead of 'Required' or revise the filter logic.

Pending Time Based Workflow Action

If there is a pending Time Based Workflow Action on the lead that the user is attempting to convert the system will prevent the user from converting the lead and display the following error:

"Error: Unable to convert lead that is in use by workflow"


Missing required fields on the destination object

If required fields on the Account, Opportunity, or Contact object are not mapped in the Lead Field Mapping or not filled in on the Lead an error message will be presented to the user.  The fields may be required due to Field Level Security. 

This message will look similar to this:

"Error: System.DmlException: Insert failed. First exception on row 0; first error: REQUIRED_FIELD_MISSING, Required fields are missing: [CE / WFD Description]: [CE / WFD Description] (System Code)

 

Custom Apex Error

Custom apex errors are caused by custom code not running correctly within your organization. The Apex code can be written on the Lead, Account, Contact, Opportunity or related Custom Object.

This type of error will display like this:

"Error:Apex trigger {Apex Trigger Name} caused an unexpected exception, contact your administrator:..."

To correct this error the custom Apex code will need to be examined by a developer for further troubleshooting. 





promote demote