Master Odoo ORM for Efficient Data Operations

This skill teaches Odoo's ORM in depth: reading and writing records via search(), browse(), create(), write(), and unlink(); building domain filters for views and server actions; implementing computed, stored, and related fields; and avoiding common performance pitfalls like N+1 queries. Worked examples cover a domain-filtered search for confirmed sale orders within a date range, with the crucial gotcha that dates must be passed as 'YYYY-MM-DD' strings in domain tuples rather than Python date or datetime objects, since the ORM serializes strings correctly but not raw date objects; a computed, stored field such as total_order_count recalculated via @api.depends on a related one2many field; and a bulk-write pattern that updates an entire recordset in a single write() call instead of looping and writing per record, which triggers a separate query for every record in the loop.

Use it when writing search, browse, create, write, or unlink calls, building complex domain filters, implementing computed, stored, or related fields, or debugging slow queries and optimizing bulk operations. It does not cover cr.execute() raw SQL patterns in depth - use the Odoo performance tuner skill instead for SQL-level optimization - nor partitioning strategies for stored computed fields at scale, nor transient models (models.TransientModel) or wizard patterns. It also notes that ORM behavior can differ slightly between Odoo SaaS and On-Premise due to configuration overrides.

Given a description of the desired data operation, it produces correct, idiomatic Odoo ORM code with explanations, or a performance review of existing ORM code that flags anti-patterns like calling search() inside a loop.

Targets the Odoo ORM API directly - recordset methods like mapped(), filtered(), sorted(), search_count(), and with_context() - with no external tooling required beyond an Odoo instance or module to run the generated code against. These recordset methods are meant to replace manual Python loops over records: mapped() extracts a field's values (or chains through relations) across an entire recordset in one call, filtered() narrows a recordset by a condition without a manual list comprehension, and sorted() orders a recordset by a key function, all evaluated by the ORM rather than iterated in application code.

Odoo developers writing or optimizing module code who need idiomatic ORM patterns and a checklist of common performance killers - search() inside a loop, raw datetime objects in domains, unnecessary sudo() use, and len(search()) instead of search_count() - to catch before shipping. Activation is straightforward: mention @odoo-orm-expert with a description of the data operation needed, receive idiomatic code with explanations, and optionally ask for a targeted performance review of existing ORM code afterward.