Filter Odoo records using ORM domain operators and avoid computed-field pitfalls

domain: odoo · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Build domain filters as lists of triples: [('field_name', 'operator', value)]; supported operators include '=', '!=', 'like', 'ilike', 'in', 'not in', '>=', '<='
  2. Combine conditions with logical prefixes: ['&', condition1, condition2] for AND, ['|', condition1, condition2] for OR; the default when listing multiple conditions without a prefix is AND
  3. Before filtering on a field, check whether it is a stored vs computed field using the model's fields_get() method or the Odoo source; stored fields map to database columns and are filterable
  4. For non-stored computed fields, retrieve all candidate records and filter in Python/application code — attempting to filter on them via the ORM domain will raise an error or return empty results
  5. Use 'limit' and 'offset' kwargs in search_read to paginate results and avoid loading entire tables

Known gotchas

Related routes

Perform record CRUD via Odoo external API (XML-RPC or JSON-RPC)
Odoo External API · 5 steps · unrated
Implement offset-based pagination and field filtering when querying NetSuite SuiteTalk REST collections
docs.oracle.com/en/cloud/saas/netsuite · 6 steps · unrated
Build structured filters for GSA Auctions listings using the API's field reference and OpenAPI schema
gsa.github.io · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans