TMContest Test

Managing Custom Fields

Custom Fields (/custom-fields) is Coordinator-only. It lets the district add its own fields on top of the built-in ones, without waiting on a code change.

Scope

Every field belongs to one scope — Contest, Helper, Contestant, or Task — which decides where it shows up.

Field types

Text, Textarea, Date, Number, Checkbox, Select, or File. A Select field needs at least one option.

Creating a field

Pick a scope, give it a short key (lowercase letters, numbers, and underscores only — this is its permanent identifier), a label, and a type. Add help text and mark it required if needed.

Editing a field

Label, help text, type, options, required, and sort order can all be changed after creation. The key and scope can't — changing either would orphan every value already stored under the old identifier.

Be careful changing a Select field's options or a field's type after it's in use: values already saved elsewhere under the old options won't automatically match the new ones, and nothing here warns you or migrates that data for you.

Archiving

Archiving a field hides it from every form without deleting anything already saved under it — the data stays put, it just stops being editable through the field. Unarchive to bring it back.