Add support for conditions on create and delete actions on One2Many fields.
auto_awesome What this module does
AI-generated from the code · Odoo 18.0Lets you show or hide the Add a line and Delete buttons on embedded lists (one-to-many fields) depending on values in the current record, using conditions written in the view.
This module changes how embedded lists inside a form behave. In Odoo, a one-to-many field (for example, the order lines inside a sales order) is shown as a small list with an "Add a line" button and a delete option. Normally those buttons are always available, or controlled only by access rights.
With this module, a developer can put a condition on the list definition itself, and the buttons appear or disappear automatically as the user changes the form. For example, the Add a line button can be hidden once a certain status is reached, or the delete option can be disabled when a field on the parent record has a particular value.
The condition is evaluated in the browser each time the list is displayed, using the current values of the record. If the condition cannot be understood, the module simply ignores it and writes a warning in the browser console instead of breaking the screen.
It only affects lists shown in edit mode; read-only lists are not changed. It does not add menus, reports, scheduled jobs or database fields. It works together with the standard web client and the base module.
Depends on
Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 7 confirmed, 2 with no information of 9 versions.
Sources · Odoo 12.0
Confirmed on 2026-11-03 in branch 12.0 of OCA/web.
terminal Installation and usage
OCA documentation · Odoo 18.0Usage
Source · Odoo 18.0Odoo by default support:
with this module you can:
It works in any tree view, so you can use it in One2many.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.