The problem with post #13 is that, by design, we do not validate missing values on update requests (because they are assumed to be missing because the user hasn't changed them). We are discussing how best to deal with this issue.
The problem in post #14 is a client-side problem with validating fields with a conditional "required" validator, specifically when editing in a ListGrid: it is not to do with the "notNull" condition as such. We have made a change to correct this; it will be in tomorrow's 11.1d / 5.1d builds.
The problem in post #14 is a client-side problem with validating fields with a conditional "required" validator, specifically when editing in a ListGrid: it is not to do with the "notNull" condition as such. We have made a change to correct this; it will be in tomorrow's 11.1d / 5.1d builds.
Comment