Nelson Inácio wrote:
Arco van der Velden wrote:
Nelson Inácio wrote:
The problem is numeric default value is 0, string default value is "", both are different from null. So the database accept these values. Only crud screen will block the update.
The CRUD screen only blocks the update if you defined the attribute in screen mandatory as well and if you check for a valid form in your screen action, if not the record will be added wihout any warning or error.
It's strange, I already had situations where I add a mandatory field and when try to update with a process executed outside of crud screen, gives database constrain error. Unless the behavior change on recent versions
Think this is only on foreign keys and not on "normal" attributes.The problem is numeric default value is 0, string default value is "", both are different from null. So the database accept these values. Only crud screen will block the update.
The CRUD screen only blocks the update if you defined the attribute in screen mandatory as well and if you check for a valid form in your screen action, if not the record will be added wihout any warning or error.