Validation Rule Behavior Differs between Lightning and Classic?
I have a validation rule that fires unexpectedly when I'm using Lightning but if I switch to classic UI the rule works as expected. Has anyone seen this?
7 commentaires
@Rodrigo Rocha - The issue was not really fixed per se (it's really a quirk). I have decided to train users around it. It only happens if user tries to update the Stage using the Path component instead of editing the stage value directly.