Build and Refine Odoo XML Views

Odoo XML Views Builder generates and reviews view definitions for Odoo models. Its scope includes Form, List, Kanban, Search, Calendar, and Graph views, together with visibility modifiers, group restrictions, domains, context, and widgets. The workflow accepts either a description of the desired view or existing XML that needs correction.

The form example defines an ir.ui.view record for a patient model. It includes a header action button, a statusbar field with visible states, a title, a notebook tab, grouped fields, and activity tracking through chatter. These elements illustrate how a complete view definition combines model fields, actions, layout, and display behavior.

The Kanban example groups records by state and declares the fields used by the card template. The card displays a name and related doctor field within the view's templates. Alongside these examples, the skill covers requests for tabs, smart buttons, color coding, progress bars, search filters, and group-by options.

Use it when creating a form or list for a custom model, extending an existing view with fields or tabs, building a Kanban presentation, or adding search behavior. It also helps review view XML for common version-related mistakes.

The stated version range is Odoo 14 through 17. Visibility syntax must match the target: older versions use attrs-based modifiers, while Odoo 17 uses inline expressions. The skill warns against carrying attrs into version 17. Chatter markup also differs between version 17 and earlier versions, so the same XML should not be assumed suitable for every target.

OWL JavaScript widgets and client-side component development are outside scope. Search panels are not fully covered, website QWeb views require separate guidance, and Enterprise Cohort and Map views are excluded.

Inputs include the target Odoo version, model, fields, intended view type, visibility conditions, access groups, and layout requirements. Existing XML can instead be supplied for review. Outputs are complete view definitions or corrections to common mistakes.

A form-header action button uses this pattern:

                <button name="action_confirm" string="Confirm"
                    type="object" class="btn-primary"
                    invisible="state != 'draft'"/>

The workflow keeps business behavior in Python model methods rather than embedding it in view XML. It also advises using a dynamic model domain when appropriate instead of hardcoded domain strings in the view. Clear labels and version-appropriate activity markup make generated definitions easier to inspect.

View records use Odoo's ir.ui.view model and reference fields on the associated business model. Object buttons call Python model methods, while widgets such as statusbar control field presentation. Activity tracking uses chatter. The related odoo-qweb-templates skill is the separate reference for website QWeb work.

It serves people building or maintaining Odoo model interfaces who need XML matching the installed version. It is particularly useful for custom-model screens and targeted extensions of existing views.