Column Selections
Column selections define which fields appear in a record list.
They control the visible columns, labels, and field paths used when users scan, compare, export, or process records in list view. A column selection does not decide which records are included. That is the role of a Query, search, or module-level filter.
Column Purpose
Scanning Records
A good column selection helps users recognise records quickly.
Most default selections should include the main identifying fields, useful status information, and a small number of fields that support the module's main workflow.
Comparing Records
Some column selections are designed for comparison.
For example, a review workflow might need status, category, score, responsible person, and last updated date. A scheduling workflow might need date, time, location, capacity, and staffing information.
Exporting Records
Column selections can also support exports.
An export-oriented selection may include fields that are not needed for everyday browsing but are required for a spreadsheet, reporting process, mailing list, or handover to another system.
Default Column Selection
First List View
A module can define the default column selection used when the list view opens.
This default should usually be compact. It should show enough information for users to understand the records without turning the table into a full database dump.
Field Choices
Default columns should favour fields that are stable, readable, and useful for common work.
Good candidates include names, titles, dates, statuses, categories, responsible users, locations, and compact relationship labels. Raw IDs, timestamps, long text fields, and technical bookkeeping fields should usually be avoided unless users specifically need them.
Formatting
Some columns need formatting information.
Dates, times, booleans, relationship labels, and calculated display fields should be shown in a form that users can scan. Where a display accessor already combines information clearly, it may be better than showing several separate technical fields.
Additional Column Selections
Workflow-Specific Selections
A module can offer different column selections for different tasks.
For example, a People module might have one selection for contact work, another for accreditation, and another for finance. Each selection can use the same records but show a different set of fields.
User-Saved Selections
Users can store column selections for later reuse.
This is useful when a user regularly needs a particular table layout for checking, exporting, reporting, or operational work.
Prepared Selections
Administrators can prepare column selections for common workflows.
Prepared selections reduce repeated setup work and make it easier for users to start from a shared view of the data.
Relationship to Queries
Visible Fields
Column selections decide which fields are visible for the current records.
Queries decide which records are shown. The two are often used together, but they remain separate choices.
Example
A query might find all applications with the status "Ready for review".
One column selection could show applicant name, category, submitted date, and review status. Another could show contact details, organisation, language, and consent fields for communication work. The records are the same; the visible information changes.