Summary of "¿Odoo va lento? El error fatal del @api.depends (compute field)"

Summary (Technological Concepts / Product Analysis)

The video discusses how to work efficiently with “calculated fields” (computed fields) in Odoo, focusing less on the compute logic itself and more on the @api.depends decorator.
Key concept: @api.depends controls when the computed field is triggered and recalculated.
- In the example, an AI-created computed field assigns a commission rule.
- The computed field should recompute only when the relevant commercial data changes (e.g., when the “commercial”/sales-related fields change).
- With dependencies defined correctly, recalculation doesn’t happen unnecessarily, which is crucial for performance.

If @api.depends is not defined properly, the computed field can execute more often than needed.
This leads to real-world symptoms like: “Odoo is slow for me.”
The creator claims this is a frequent, practical cause of slowness.

Instead of relying only on auto-generated code, the speaker examines how Odoo implements similar fields.
Example used: the user_id field, which depends on the client; selecting a client automatically assigns the corresponding salesperson.
The recommendation is to replicate proven Odoo behavior in custom fields so the implementation aligns with official development standards, not just correctness.

The speaker draws on personal experience and client feedback (e.g., “Clients have told me…”).
They also use Odoo’s built-in field behavior (such as user_id depending on client) as the primary reference point for best practices.