week_days

Recurring schedules need a compact way to answer one question: which days of the week does this apply to? Odoo's answer is week_days, a view widget that renders a single-row table with a header of weekday names and a checkbox under each.

It is deliberately rigid. The widget declares fieldDependencies for seven boolean fields with fixed names, sun through sat, which means the model behind the view must define exactly those fields. In exchange, the view XML stays a one-liner: the dependencies make the ORM load the seven fields automatically, so you do not add them to the arch yourself. In core it powers the lunch app's supplier availability and alert schedule.

Weekday patterns show up everywhere operations meet a calendar: which days a supplier delivers, which days an alert fires, which days a shift or service runs. Storing them as seven booleans keeps the data model trivially filterable, and this widget keeps the UI honest, seven checkboxes users cannot mistype, instead of a free-text field like Mon-Wed-Fri that no one can query.

The locale-aware ordering is a small detail with real effect for international teams: the same form shows Sunday first to a US user and Monday first to a Belgian one, matching how each reads a week. Nobody configures that; it follows the language settings automatically.

How core places it (lunch supplier)

<label for="sun" class="d-none"/>
<field name="sun" invisible="1"/>
<widget name="week_days"/>

From lunch_supplier_views.xml. The invisible field and hidden label are only there to give the group a label anchor; the widget itself loads all seven fields through its dependencies.

Using it on a custom model

# model: seven booleans with the exact names
sun = fields.Boolean()
mon = fields.Boolean()
# ... tue, wed, thu, fri, sat

<widget name="week_days"/>

That is the whole integration: fields with the right names, one widget element in the form.

The ordering logic is one line worth understanding. The component keeps a fixed array starting at Sunday and rotates it by localization.weekStart % 7, the week-start value Odoo derives from the user's language. The header labels are not hardcoded either; each column prints record.fields[day].string, so relabeling a field in Python, or translating it, changes the column header automatically.

Editing goes through record.update({ day: checked }) per click: the form becomes dirty and standard save or discard semantics apply, and readonly on the view disables every checkbox. The calendar module demonstrates the intended extension path: CalendarWeekDays subclasses the component, swaps the template, reuses the same fieldDependencies, and registers under its own name calendar_week_days for event recurrence, where clicking the day label itself toggles the value.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. We read the widget's file on the public development branch at the time of writing; the branch is unstable and this page will be re-verified after release.

No functional changes: the seven dependencies, the locale rotation and the registration are identical to Odoo 19. The only movement is the migration to the new Owl typed-props syntax, which affects JavaScript patches and nothing in XML.