I made a field mandatory via client script, the red asterisk appears on the page, but it can be saved without populating.

If that doesn't work maybe shift your logic to save and pop an alert / message.

I've found that the

isMandatory

property doesn't actually add the validation that you'd expect it to, it just adds the asterisk - it's pretty weird, but using it in conjunction with custom validation in

saveRecord

generally works fine.

saveRecord

works. Thanks

Oh interesting, I thought that maybe it was just inconsistent but I've stopped relying on it at all since I hadn't noticed a pattern. Good to know that it may be able to work on its own for native fields though.

No, I'm wrong. The native fields are mandatory according to field level validation, not client scripting.

Ah yeah, that makes sense. For what it's worth, the documentation for

N/currentRecord

doesn't list

isMandatory

as read only, so this seems like a defect to me (at least incorrect documentation). But good luck getting NS support to agree with that assessment...