invalid_locked_fields

A collection's "lockedFields" setting is refused: it isn't an object naming each locked field and a text, number or true/false default; it names more than 10 fields; a field isn't declared in the collection's shape, is retired, is the wrong type for its default, or is also named in "openFields"; or the collection's rule is admin_write, public_read, addressed or app_only, where no app session ever writes a record, so locking one would do nothing (it works on private, shared, community and direct).

Status: HTTP 400 · Data

What happened

A collection's "lockedFields" setting is refused: it isn't an object naming each locked field and a text, number or true/false default; it names more than 10 fields; a field isn't declared in the collection's shape, is retired, is the wrong type for its default, or is also named in "openFields"; or the collection's rule is admin_write, public_read, addressed or app_only, where no app session ever writes a record, so locking one would do nothing (it works on private, shared, community and direct). gemmein dev, npx gemmein sync and the dashboard's collection settings all refuse it before anything changes; the message names the fix.

Read more

• invalid_locked_fields in the error table
• Collections, filters and totals
• Data: what happens if…
• Changelog: when codes were added or removed