Skip to main content
Hello,

 

I have have a process builder flow built on the Contact object and I only want it to trigger should a Contact be edited.

 

I do not want the flow to trigger if a Contact is manually created direct on the Contact object or if it is created via the Lead Conversion process.

 

I've seen a few posts stating to use the ISNEW() function and/or check the 'Do you want to execute the actions only when specified...' check box on the Criteria. Both of these actions work as expected when I create or edit a Contact direct on the Contact Object.

 

My issue is when I convert a Lead to Contact, I get the following errors:

 

Process Builder causing issues when converting a Lead to Contact

 

Text:

 

Error: System.DmlException: Insert failed. First exception on row 0; first error: CANNOT_EXECUTE_FLOW_TRIGGER, The record couldn’t be saved because it failed to trigger a flow. A flow trigger failed to execute the flow with version ID 3015B000000A4hi. Flow error messages: <b>An unhandled fault has occurred in this flow</b><br>An unhandled fault has occurred while processing the flow. Please contact your system administrator for more information. Contact your administrator for help.: [] Class.leadconvert.BulkLeadConvert.handleRegularContactInserts: line 367, column 1 Class.leadconvert.BulkLeadConvert.convertLead: line 99, column 1

 

And I also receive the following text in a Flow Aplication Error email:

 

Error element myPreWaitDecision_myWait_myRule_46 (FlowDecision).

 

The flow failed to access the value for myVariable_current.RecordType.DeveloperName because it hasn't been set or assigned.

 

If I deactivate the process builder flow, I can convert a Lead to Contact with no issues.

 

Any pointers or help on this would be greatly appreciated.

 

Many thanks,

 

Emma.

 

 
7 Antworten
  1. 11. Okt. 2017, 15:02
    Issue is now resolved :) I switched the RecordType.DeveloperName references to RecordType.Name.

     

    I'm not 100% sure why this has resolved the issue, I can only think it has something to do with the custom trigger we have.

     

    Thanks for your help.
0/9000