Skip to content

Scope and limitations

This portal combines two sources:

  1. A database-specific runtime snapshot containing model and field metadata plus standard ORM methods.
  2. Curated integration guidance based on Odoo 19's documented external API and ORM behavior.

Covered

  • Technical and human model names
  • Installed-module ownership reported for each model
  • Persistent versus transient model status
  • Field name, label, type, required, readonly, storage, relation, inverse, relation table, and help metadata
  • Static selections, domains, field access groups, deletion policy, compute/dependency/related metadata, company dependence, tracking, indexes, and module provenance
  • Declared model read/create/write/delete ACLs evaluated for the exporting user's effective groups
  • Applicable record-rule declarations for the exporting user
  • Twelve standard ORM methods captured by the exporter
  • JSON-2 request patterns and legacy JSON-RPC migration guidance

Not fully covered

  • Exhaustive custom and model-specific business methods; high-value methods are curated from verified workflows
  • Method decorators, complete signatures, and side effects outside the standard method list
  • Current record contents or record counts
  • Dynamic selection functions and runtime-expanded dynamic domains
  • Onchange behavior, Python constraints, SQL constraints, and every state-dependent workflow rule
  • Defaults, which must be resolved with default_get under the request's user/company/context
  • Permissions for API users other than the exporting identity
  • Controller endpoints outside the model API

Reference, not a permission guarantee

An allowed ACL does not guarantee a successful operation. Record rules, field groups, allowed companies, current record state, locks, and Python/SQL constraints still apply. Test with the production integration identity and expected company context.

For high-risk workflows, especially accounting entries, payments, reconciliation, stock valuation, and tax reporting, review the owning Odoo module and expose a narrow server-side method with a stable contract.