INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST
The value is not allowed in a restricted picklist. The message reads bad value for restricted picklist field: <value>. Common causes How to fix
The value is not allowed in a restricted picklist. The message reads bad value for restricted picklist field: <value>. Common causes How to fix
The selected lookup value does not satisfy the field’s lookup filter. Users see “Value does not exist or does not match filter criteria.” Common causes How to fix
A field value is invalid in context, even though its format is correct. Common causes How to fix
The user has no right to perform this operation on the record itself. Common causes How to fix
The user can edit the record being saved but lacks access to a related record the save touches. Common causes How to fix
The record references an ID that does not exist or is not valid for that field. Common causes How to fix
A duplicate rule with the Block action stopped the save. This is different from DUPLICATE_VALUE, which is a field-level constraint. Common causes How to fix
A field marked Unique already holds the value on another record. The message includes the ID of the existing record. Common causes How to fix
A field that is required at the database level was left blank. The message lists the fields, for example Required fields are missing: [LastName]. Common causes How to fix
A validation rule, a flow custom error, or an addError() call in a trigger blocked the save. The message text is whatever the rule’s author wrote. Common causes How to fix