odoo-crossversion · diff
git:20260918.378d445 to git:20260918.bd10555
10 added, 2 removed. Audit A to A.
---
name: odoo-crossversion
description: How the compatibility layer resolves model/field names across Odoo 10-19 so a single tool call works everywhere. Reference when a field is dropped or a model name differs by version.
---
# Cross-version behavior (Odoo 10-19)
The MCP server routes every model/field name through a compatibility layer
before hitting the ORM. You write against the **modern** name; it resolves to
whatever exists on the target version.
## Model name resolution
+ Accounting is a **merge, not a rename**: `account.move` (journal entries)
+ exists on all versions 10-19. On v10-12 `account.invoice` is a **separate**
+ invoice model folded into `account.move` at v13.
+
| You pass | Odoo ≤ 12 | Odoo ≥ 13 |
|----------|-----------|-----------|
- | `account.move` | → `account.invoice` | `account.move` |
- | `account.move.line` | → `account.invoice.line` | `account.move.line` |
+ | `account.move` | `account.move` (journal entries — never rewritten) | `account.move` |
+ | `account.move.line` | `account.move.line` (never rewritten) | `account.move.line` |
| `account.invoice` (historical) | `account.invoice` | → `account.move` |
+ | `account.invoice.line` (historical) | `account.invoice.line` | → `account.move.line` |
+
+ > On v10-12 name the model you actually mean (`account.invoice` for invoices,
+ > `account.move` for journal entries), especially for writes/deletes.
| You pass | Odoo ≤ 18 | Odoo ≥ 19 |
|----------|-----------|-----------|
| `stock.package` | → `stock.quant.package` | `stock.package` |
Unknown/unchanged models pass through untouched.
## Field resolution
- `account.move.line.analytic_distribution` ↔ `analytic_account_id` (boundary v16).
- Removed fields return a **dropped_fields** warning in the response instead of
failing the whole call (e.g. `product.template.uom_po_id` on v17+,
`res.partner.company_type` on v19+ → use `is_company`).
## Capabilities
- API keys exist from v14 (older needs a password).
- `/jsonrpc` rejects API keys on v17+ — the transport auto-falls back to XML-RPC
and logs one warning; you don't need to do anything.
- Translations use the native `update_field_translations` API on v16+, and a
language-context write on older versions — `odoo_translate_set` picks the path.
## When a call still fails
A `CompatError` carries a human-readable remediation. Boundaries marked
"best-effort" in `server/src/odoo_mcp/compat/deltas.py` (e.g. the stock package
rename) can be confirmed against the live instance and adjusted there — the map
is plain data covered by table-driven tests.