Submit For Approval with validation errors/process builder, behaves different in lightning in comparison with Classic.
Last updated 2022-03-16 ·Reference W-6197882 ·Reported By 23 users
While doing submit for approval which has an approval workflow that does a field update, and also kicks off a Process Builder process, leading to a below validation rule error on the object in question.
Can’t Save Record
We can't save this record because the"XXX" process failed. Give your Salesforce admin these details. This error occurred when the flow tried to update records: FIELD_CUSTOM_VALIDATION_EXCEPTION: "XXX" . You can look up ExceptionCode values in the SOAP API Developer Guide. Error ID: 932910395-189212 (706428255)
Via Lightning UI the submit for approval still gets approved on the original approval field update which should not commit in that case. While the same does not happen via Classic UI
The Classic and Lightning code path is completely different, hence the difference in behavior is seen.
1) You have some object - custom or standard, shouldn't matter which has a validation rule.
2) You have an approval process that updates a field at some point.
3) The field update from point 2 causes Process Builder process to fire.
4) The process update updates some field, which is a direct violation of the validation rule from step 1
In classic you will see an error in UI and the record is not approved, while the same is approved via lightning.
Use classic UI
Reported By (23)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.