field_locked

A create or update named a field your collection's "lockedFields" setting locks — refused by naming it at all, whatever the value, even the field's own declared default.

Status: HTTP 403 · Data

What happened

A create or update named a field your collection's "lockedFields" setting locks — refused by naming it at all, whatever the value, even the field's own declared default. Only the business side changes it: your server (a secret key), a relay, an Edge function, a view's move action, or the dashboard. A create that leaves it out is born with the declared default already written.

Read more

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