You need to sign in to do that
Don't have an account?
msaz87
Process Builder error: Record rolled back because not all records were valid and the request was using AllOrNone header
I'm getting the following error in a Process Builder rule, and I'm not sure why. The rule fires when a user lookup field on the Account changes. When that field changes, it changes all of the Account's Contacts ownerId to equal the new field value.
Here's the error:
Here's the error:
An error occurred at element myRule_1_A1 (FlowRecordUpdate). UPDATE --- UPDATE FAILED --- ERRORS : (ALL_OR_NONE_OPERATION_ROLLED_BACK) Record rolled back because not all records were valid and the request was using AllOrNone header --- for SFDC record with ID : 003A000001VHDehIAH, This report lists the elements that the flow interview executed. The report is a beta feature. We welcome your feedback on IdeaExchange. Flow Details Flow Name: Update_Contact_to_Pipeline_Rep Type: Workflow Version: 1 Status: Active Flow Interview Details Interview Label: Update_Contact_to_Pipeline_Rep-1_Account Current User: xxUserxx (005A0000005FohB) Start time: 3/2/2016 2:24 PM Duration: 28 seconds How the Interview Started Chris Thames (005A0000005FohB) started the flow interview. Some of this flow's variables were set when the interview started. myVariable_old = 001A0000014JsaDIAS myVariable_current = 001A0000014JsaDIAS RecursiveCountVariable = 0.00 ASSIGNMENT: myVariable_waitStartTimeAssignment {!myVariable_waitStartTimeVariable} Equals {!Flow.CurrentDateTime} Result {!myVariable_waitStartTimeVariable} = "3/2/2016 2:24 PM" DECISION: isChangedDecision2_myRule_1_Pipeline_Rep_c Executed this outcome: isChangedRule_2_myRule_1_Pipeline_Rep_c Outcome conditions: and 1. {!myVariable_old} (001A0000014JsaDIAS) Is null false 2. {!myVariable_old.Pipeline_Rep__c} (005A0000007DuG5IAK) Does not equal {!myVariable_current.Pipeline_Rep__c} (005A0000005FohBIAS) Logic: All conditions must be true (AND) DECISION: myDecision Executed this outcome: myRule_1 Outcome conditions: and 1. {!isChangedRule_2_myRule_1_Pipeline_Rep_c} (true) Equals true 2. {!myVariable_current.Pipeline_Rep__c} (005A0000005FohBIAS) Is null false Logic: All conditions must be true (AND) RECORD UPDATE: myRule_1_A1 Find all Contact records where: AccountId Equals {!myVariable_current.Id} (001A0000014JsaDIAS) Update the records’ field values. OwnerId = {!myVariable_current.Pipeline_Rep__c} (005A0000005FohBIAS) Result Failed to update records that meet the filter criteria. Error Occurred: UPDATE --- UPDATE FAILED --- ERRORS : (ALL_OR_NONE_OPERATION_ROLLED_BACK) Record rolled back because not all records were valid and the request was using AllOrNone header --- for SFDC record with ID : 003A000001VHDehIAH,
Thanks,
Parker
I'm brand new to Process Builder -- can you give me a little more of a walkthrough on how to achieve that?
Thanks,
-Matt
*Both fields in the conditions for "Pipeline Rep Changes" are the same
For more on the AllOrNone header see this page I found https://developer.salesforce.com/docs/atlas.en-us.198.0.api_meta.meta/api_meta/meta_allornoneheader.htm
Do you know any way to stop the PB if the number of matched records exceeds a certain amount?
https://help.salesforce.com/apex/HTViewHelpDoc?id=process_limits.htm&language=en_US
Parker
https://developer.salesforce.com/forums?id=906F00000008lW0IAI
Oh, and by the way, don't mark this question as solved by giving it a best answer, someone with a good idea might come along and answer your question, unless you're content with not having a process that works for you after all this.
If you have any more questions about processes or formulas, I'd be happy to help.
Thanks again,
Parker
Do you manage to solve this issue? I am having the same error message when importing 200 opportunities which will trigger a process flow to update the Account.
Currently the only workaround spotted is to reduce the batch size from 200 to 30 and the import will work flawlessly.
Good luck!
I ran into a very similar error.
We have a custom object that looks up to the Opportunity object.
When an Opportunity is marked as "Closed Lost" we have a process that updates the custom objects related to that Opportunity.
I found that the error came from a validation rule.
Interestingly, the record that was specified in the error email WAS NOT THE RECORD THAT WAS VIOLATING THE VALIDATION RULE.
I highly suggest taking a look at your Contact validation rules.
Maybe do a test where you disable all of them and then try to execute this process again.
I bet it'll work for you.
That won't tell you WHICH contact was violating the validation rule, but it'll at least put you on the right path.
I'm interested to see if this works for you.
Thanks!