Fields That Fill Themselves In

Part 4 of 11: Fields That Fill Themselves In

---

I keep a list of field recording sessions: where I went, when, and whether the audio was usable. The whole value of that list is that I actually add to it, and the enemy of actually adding to it is friction. Every field I have to fill by hand is a small tax, and enough small taxes and I just stop.

Defaults are how you cut the tax. A default is the value a brand new row starts with, so the common case is already typed for you and you only touch what's different this time. It sounds minor. It's the difference between a list I maintain and a list I abandon.

Defaults know what kind of field they're on

The nice part is that the default control isn't one dumb text box for everything. It changes shape based on the field type, so the value you set is actually the right kind of value.

A field's Advanced panel with the Default Value control visible alongside Required and Help Text

• Dates are the standout. A date field can default to "the current date when the row is created," so every session I log is stamped with today automatically and I never type a date again unless I'm backfilling. Or you can pin a specific date, or leave it blank. That "today, whenever the row is born" option is the one I turn on almost every time.
• True / False fields default to true, false, or a third thing: Neither. An optional yes/no isn't really two states, it's three, because "I haven't decided" is real. Neither leaves the field genuinely unset instead of quietly lying that the answer is no. If you make the field required, it drops the ambiguity and starts at False.
• Text, number, and choice fields take a plain default. A status field that starts at "Planned," a quantity that starts at 1, a category that starts on the value you use most.

Why this matters more than it looks like it should

Set a good default and every new row arrives already agreeing with your most common case. My sessions list opens a new row already dated today, already set to "Planned," and all I do is type the place. That's a two-second entry instead of a twenty-second one, and the two-second version is the one that survives a busy week.

There's a subtle honesty benefit too, the tri-state boolean one. A lot of tools force a yes/no to be one or the other, so "unknown" gets recorded as "no," and later you can't tell the difference between "definitely not" and "nobody checked." Neither keeps that distinction. It's a small thing that keeps your data from telling you comfortable lies.

Good defaults are the least glamorous feature in this whole series and the one that quietly decides whether you keep using a list. Set them once, benefit on every row.

Next I want to open the hood. Everything you've built with the visual builder is really a small schema, and seeing it changes how you think about what a list can be.

Adron