You need to sign in to do that
Don't have an account?

Validation Rule stops Process Builder to fire
Hi All,
I have a Process Builder and a Validation Rule on the Opportunity Object.
The Validation Rule is meant to stop the users from modifying an Opportunity once Closed Won, apart from Admins.
And the Process Builder is checking if "[Opportunity].IsClosed = TRUE, and updates the Close Date = TODAY().
Error message:
Both the Process Builder and the Validation Rule work fine, but activated separately.
Is there a way to stop the users from modifying the Closed Won Opportunity, but allow the process to change the Close Date for the users?
Thanks.
I have a Process Builder and a Validation Rule on the Opportunity Object.
The Validation Rule is meant to stop the users from modifying an Opportunity once Closed Won, apart from Admins.
AND (ISPICKVAL(PRIORVALUE(StageName),"Closed Won"), CASE($Profile.Name, "ProfileName1",1, "ProfileName2",1, 0)=0 )
And the Process Builder is checking if "[Opportunity].IsClosed = TRUE, and updates the Close Date = TODAY().
Error message:
> The flow tried to update these records: null. This error occurred: > FIELD_CUSTOM_VALIDATION_EXCEPTION
Both the Process Builder and the Validation Rule work fine, but activated separately.
Is there a way to stop the users from modifying the Closed Won Opportunity, but allow the process to change the Close Date for the users?
Thanks.
Hope that your day is off to an amazing start. We've edited your validation rule to meet your criteria. Please test and report back if you have any problems. Hope this helps and may God bless you abundantly.
Best Regards,
Anthony McDougald
AND(
TEXT(StageName)== "Closed Won",
$Profile.Name <> 'System Administrator'
)
Thanks,
Maharajan.C
I hope you're well and thanks for coming back to me.
I have amended my VR as per your suggestion, but unfortunately, the process still fails.
Thanks.
Thanks a lot for your suggestion. I have also tried yours, but unfortunately, I am unable to Closed Won the Opportunity.
Thanks.
Hope that your day is off to an amazing start. Apparently, this is an issue that occurs and will need a work around. For a Process Builder, you would need a custom field to use to bypass the VR. However, we would recommend using APEX as this can automate your solutions while fulfilling the needs of the VR. Hope this helps and may God bless you abundantly.
Best Regards,
Anthony McDougald
Thanks for your reply. I have managed to resolve this now.
Thanks a lot.
I'm having a similiar issue. How did you resolve this issue.
Thanks!