I am developing an app where I am throwing an error on FVC of a subtable (main) field. The error is thrown correctly, but I was still able to save the parent record so I had to add the validation on the Before Save event on the parent. Is that expected behavior?
Yes. If you want to prevent save you have to check for your condition in a trigger. It is the trigger that protects data integrity, not any UI component. Hooking the same check up to a field value changed event is only going to improve user experience, not protect data integrity.
4 Likes