Fields

Fields are the details an item carries. A part might have a name, a quantity, a location, and a photo. A machine might have a model, a firmware version, and a purchase date. Every module comes with sensible fields already, and you add your own whenever you want to track something more.

Custom fields

You can add a field of whatever type fits what you're recording:

• text, for names and notes
• numbers, for counts, measurements, or prices
• yes / no, for a simple flag
• a choice from a list you define, like a status or a category
• a date, for due dates, arrivals, or when something was bought
• a URL, which can render as an image when a picture is the point (items also carry a built-in photo)
• links between items come from modules and bundles, which contribute relation fields where records should point at each other

A new field shows up in the item's form, and you can add it as a column, group a kanban by it, or filter on it in any view.

Computed fields

Some fields you don't fill in. A computed field builds its own value from the other fields on the item, and keeps itself up to date.

Two common cases:

• A name assembled from parts. A vehicle's display name can just be {{ year }} {{ make }} {{ model }}, instead of retyping "2019 Honda Civic" into a name field when those three are already filled in.
• A summary pulled from related records, like when something was last serviced, what's due next, or how much you've spent on it.

Computed fields are read-only. You never type into them, and they're always current because they're worked out fresh each time the item is shown.