Appearance
Custom fields
Where custom fields are defined. What they are for, and how they differ from tags, is in Custom fields.
Defining a field
Each row is one field:
| Column | What it does |
|---|---|
| Label | What appears on the record. |
| Key | The stored identifier. Kancil suggests one from the label. |
| Kind | Decides the input control. |
| Options | For choice kinds — entered comma-separated. |
| Required | Makes the field mandatory. |
| Pos. | Order the fields appear in. |
The key
The key is the one to get right first time. It is what the value is stored under, so changing it later leaves existing values filed under the old key, where nothing will look for them.
Take the suggestion unless you have a reason not to. Changing a label later is free.
Required fields
Marking a field required affects records you create from then on. It does not retroactively invalidate records that predate it — but it does mean editing an old record may now ask you to fill in something you never had a value for.
Use it for the fields that are genuinely mandatory, and let the rest be optional.
Order
Position controls the order on the record. Put the field you fill in every time at the top; a form ordered by how it was built rather than how it is used costs a moment on every record forever.