See the inner records without leaving the list.

A drop-in OWL field widget that turns any One2many / Many2many on a list view into a compact "N items" badge — with a tabular preview that pops up on mouse hover. No drill-down click, no dialog, no extra RPC. Your buyer / AR / CS team keeps scanning the list, and gets the detail one hover away.

Sales Orders list. Hover the 12 items badge — the preview popover slides down with Product / Qty / UOM. Move your cursor INTO the popover, it stays open.

What You Get

End-to-End Setup — 5 Steps

From install to a live hover preview in under three minutes.

3

Add the widget + options dict

Inherit the list view and put widget="o2m_preview" on the field, with a small options dict describing the columns. Save.

4

Hover. Reveal.

Reload the list. Every row shows the compact N items badge. Hover — the preview popover slides in with the configured columns. Cursor can move into the popover and read the table; leaving closes it after a 200 ms grace.

Options reference

Drop-in patterns

<field name="order_line"
       widget="o2m_preview"
       options="{'fields': ['product_id',
                            'product_uom_qty',
                            'product_uom'],
                 'labels': ['Product','Qty','UOM']}"/>

<field name="invoice_line_ids"
       widget="o2m_preview"
       options="{'fields': ['name', 'quantity',
                            'price_unit',
                            'price_subtotal'],
                 'title':  'Invoice Lines'}"/>

<field name="move_ids_without_package"
       widget="o2m_preview"
       options="{'fields': ['product_id',
                            'product_uom_qty', 'state'],
                 'labels': ['Product','Demand','Status'],
                 'title':  'Moves'}"/>

<field name="child_ids"
       widget="o2m_preview"
       options="{'fields': ['name', 'stage_id',
                            'user_ids'],
                 'title':  'Sub-tasks',
                 'max_rows': 50}"/>

⚠ Pass options.fields on list views

Odoo only fetches fields that the view's arch asks for. A list-view embed like <field name="invoice_line_ids" widget="o2m_preview"/> — without options — gives the inner records only their id. The badge shows the right count, but the popover body has nothing to render.

Pass options="{'fields': [...]}" and the widget's relatedFields hook tells the loader which inner fields to fetch. Or, if you prefer, embed a hidden inner subview — <list><field name="..." optional="hide"/></list> — the loader fetches everything in that subview too. Form-view embeds usually have the inner fields already loaded, so you can skip options there and let the auto-detect take over.

⚙ How it works (technical)

• Pure OWL 2 field widget. No Python models, no data files, no migrations.
• Registered via registry.category("fields").add("o2m_preview", ...) with supportedTypes: ["one2many", "many2many"] so the arch validator stays happy.
• Reads inner records from record.data[name].records, which the list view already loaded — no extra RPC. Inner field metadata (type + Selection labels) comes from record.data[name].fields.
• Popover opened via Odoo's standard usePopover hook. The cell schedules a 200 ms delayed close on mouseleave so you can move the cursor INTO the popover without it slamming shut; the popover cancels its own close while the cursor is over it.
• Value formatter handles Many2one (display_name / [id, name] tuple), Selection (key → label), Boolean (Yes / empty), and numbers (locale formatting, integer pass-through).

Compatibility

Odoo 18.0 — Community & Enterprise  •  Single hard dependency: web (standard frontend bundle)  •  OWL 2 component, modern asset bundle

Built by Alphasoft

We build practical Odoo modules for real businesses — accounting, inventory, reporting, and the small UI patches that make daily work less click-heavy.

www.alphasoft.co.id