Open a form or list view of the model you want to customise (e.g. Sales Orders, Contacts, Employees).

The Studio panel slides in from the right. The model technical name (e.g. sale.order) is shown just below the header.

Click one of the toggle buttons: Form · List · Search · Kanban · Pivot · Graph · Cal · Gantt · Rpt

All fields on this model not yet in the view are shown with a type badge and technical name.

The field is inserted into the view. Switch to "Fields" tab to see and reorder it.

Opens the Field Wizard: choose type, label, and type-specific options. The field is created on the model and added to the view in one step.

Set: Label, Type (Object/Method or Action/XML-ID), Placement (Header or Sheet body), Style (Primary/Secondary/Warning/Danger).

All fields currently in the view are listed with drag handles.

"Unsaved changes" badge appears in footer.

Core model fields show a 🔒 and cannot be removed from the panel.

The Fields tab label changes to "Cols" reflecting column management.

Click "New / Manage List Views" below the toggle. Enter a name → Create List View, or click the open icon on an existing Studio list view to load it.

All columns currently in the list are shown. Hint: "Drag to reorder columns. Click to edit column options."

"Unsaved changes" badge appears in panel footer.

Core model columns show a 🔒 and cannot be removed.

Opens inline options for that column (see Column Details below).

Lists all model fields not yet shown as columns.

The field appears at the end of the column list. Drag-reorder it under "Cols".

Opens the Field Wizard to create a new model field which is also added as a column.

Choose whether the list is editable inline: Top (new row at top), Bottom (new row at bottom), or Not editable.

Enable/disable: no_open (row click does not open form), create, delete, import, export_xlsx.

Set a default grouping field and a default sort field with direction (asc / desc).

Add conditional row highlight rules. Choose a decoration class and enter a Python condition. Click Add Decoration. Existing decorations can be deleted with ✕.

Add custom action buttons to the list header. Set: label, icon, style, and the server action name. Click Add Button.

This is a separate save from the main panel footer Save. Applies list-level config changes.

The Fields tab label changes to "Card".

Studio auto-creates a basic kanban view with the title/name field. The card field list then becomes available.

Lists all fields on each kanban card. Hint: "Drag to reorder fields shown on each kanban card."

Updates the XPath //t[@t-name='card'] in the view arch.

Core fields (🔒) cannot be removed.

The field appears at the end of the card field list.

Select a field for the ribbon indicator. priority shows star ratings; kanban_state shows a traffic-light dot. "None" disables the ribbon.

Select an Integer field (values 0–11) for card colour highlighting. Users can then pick a colour from the card's ⋮ menu. "None" disables colour. Requires Integer, not Many2one.

Select a many2one or selection field to group the kanban by default on load. "None" = no default grouping.

Enabled (default) = clicking an empty column header opens a quick-create input. Disabled = requires opening a full form to create records.

Saves the configuration to the kanban view XML. Button appears only when changes are pending (dirty state).

Hint: "Assign fields as Row groups, Column groups, or Measures."

Studio auto-creates a basic pivot view. The field configuration then becomes available.

Lists all suitable fields not yet in the pivot view.

Numeric fields default to Meas role; others default to Row role.

The active role is highlighted. Clicking an already-active role deactivates it (field has no role).

When a date/datetime field is assigned Row or Col role, a granularity dropdown appears: Day · Week · Month · Quarter · Year.

Multiple Measure fields can be added — each appears as a separate column in the pivot table.

Writes the view name and all field roles (including date granularity) to the pivot view XML using //pivot position="replace".

Reloads the pivot field list from the server.

Hint: "Select chart type and assign Row (category) and Measure (value) fields."

Studio auto-creates a basic graph view. The field configuration then becomes available.

The internal name saved with the view. Example: Sales by Month.

Click one to set the default chart type. The active button is highlighted. This sets the type attribute in the graph view XML.

Numeric fields default to Meas; all others default to Row.

Active role is highlighted. Clicking active role deactivates it.

Writes view name, chart type, and all field roles to the graph view XML using //graph position="replace".

Reloads the graph field list and chart type from the server.

Hint: "Configure date fields, color grouping, and default view mode."

Studio auto-creates a basic calendar view and auto-detects the best available date field for Start Date. The config panel then becomes available.

Select a date or datetime field — marks where each calendar event begins. The "Save Calendar Config" button is disabled until a Start Date is selected.

Date/Datetime field for event end. If not set, each event appears as a single-day/single-time entry.

A float or integer field for event duration in hours. If both End Date and Duration Field are set, Duration Field takes precedence in the calendar view XML.

Select a field whose value is shown as the event title on the calendar. Date/datetime and many2one fields are listed.

Select a many2one field only — events are colour-coded by that field's value, with a colour legend in the calendar sidebar. Selection fields are not supported for calendar colouring in Odoo 19.

Sets the initial calendar display: Day · Week · Month (default) · Year.

When enabled (default), clicking an empty slot opens a quick-create dialog. When disabled, a full form opens instead.

The button is disabled until a change is pending (dirty) AND a Start Date is selected. Saves the configuration to the calendar view XML.

Hint: "Configure the Gantt chart fields for this model."

The Gantt view is rendered as a standalone page. Configuration is stored in ir.config_parameter.

Free-text heading shown above the Gantt chart. Example: Project Task Timeline.

Select a date or datetime field — determines where each bar begins. "Save Config" and "Open Gantt" buttons are disabled until Start Date is set.

Date/datetime field for bar end. If left as "none (1-day bars)", each bar spans exactly one day.

Select a Char or Text field — its value is displayed as text on each Gantt bar.

Select a many2one or selection field — records are colour-coded by this field's value.

Select a float or integer field (values 0–100). Renders a progress bar inside each Gantt bar showing completion percentage.

Select a many2one or selection field to create swim-lane rows (grouped Gantt). "none (flat list)" shows all bars ungrouped.

Initial zoom level of the Gantt timeline.

Saves to ir.config_parameter key drkds_studio.gantt_config.{model}. Persists across server restarts. Disabled until Start Date is selected.

Opens the Gantt chart view in the main content area. Also disabled if no Start Date is selected.

Shows all reports bound to the current model — both Studio-created (with "studio" badge) and native Odoo reports.

⎙ Print (preview), </> Edit XML (code editor), 🗑️ Delete (Studio reports only).

Required. Becomes the report action name in the Print menu. "Create Report" button is disabled until a name is entered.

PDF = qweb-pdf (downloads a PDF file). HTML = qweb-html (renders inline in the browser).

Four template cards are available:

Dropdown lists many2one fields pointing to res.partner or res.lang. Selecting one causes the report to auto-print in the recipient's language. Leave as "None (company language)" if not needed.

A scrollable checklist shows all suitable model fields. Excluded: Binary, HTML, One2many, Many2many. At least one field must be selected.

Generates the QWeb view XML (using lxml — no XML injection risk), creates an ir.actions.report bound to this model. The report immediately appears in the model's Print ⎙ action menu.

Opens the inline XML editor showing the full <t t-name="..."> QWeb template.

Common edits: add/remove <span t-field="o.field_name"/> elements, adjust styles, change layout. Note: t-field renders with Odoo's built-in formatting.

XML is validated before saving. Invalid XML is rejected with a clear error message.

Returns to the report list. Unsaved XML changes are discarded.

Triggers the Odoo report action in the current record context. PDF reports download; HTML reports render inline.

Deletes both the ir.actions.report record and the underlying QWeb ir.ui.view. Only Studio-created reports (with "studio" badge) show the delete button. Native Odoo reports cannot be deleted.

Lists all server actions for this model (both Studio-created and others).

Enter a name and write Python code. Variables: records, env, model.

When bound (green border), the action appears in the ⚙️ Action dropdown on list and form views.

Identified by the cron_name prefix. All other crons are shown read-only.

Review the code before activating to avoid unintended side effects.

name maps to the linked ir.actions.server.name (required). cron_name is the display label on ir.cron.

Lists all Studio-created menus for this model.

Parent menu is selected from a dropdown of all existing top-level menus.

A matching ir.actions.act_window is created and linked to the menu.

Shows all export templates for this model.

Enter a name and tick the fields to include. Binary, HTML, and relational fields (O2M) are excluded.

When users export data from a list view, the saved template appears as a preset in the export dialog (under Saved Exports).

The wizard auto-detects column headers and attempts to auto-map them to model fields by name similarity.

For each CSV column, select the target model field from a dropdown. Unmapped columns are skipped.

Rows are validated and imported. A results panel shows the count of created/updated records and any row-level errors.

Lists all server actions that can be bound as batch actions for this model.

When ON (green border), the action appears in the ⚙️ Action dropdown on list views when records are selected.

Controls whether the action appears on the list view's multi-select menu, the form view's Action button, or both.