Display company_dependent state of fields in "ir.model.fields" views
company_dependent value of a field can be overrided in any module. Then it can be difficult to guess this value in a odoo instance with a lot of modules.
This module is mainly intended for developers
auto_awesome What this module does
AI-generated from the code · Odoo 14.0Shows, in the technical field list of Odoo, whether each field stores a different value per company. It helps developers and administrators see which fields are company-dependent without digging into the code.
This module adds a small technical indicator to Odoo's field configuration screens. It does not change any business document; it only makes information visible.
- A new column/field called company_dependent is added to the list of fields (the technical model
ir.model.fields). - It appears on the field form view, right after the "Copied" option.
- It also appears in the tree/list view of fields, right after the "Relation" column.
- On the model form view, it is shown in the list of fields of that model, after the "Index" column.
The value is calculated automatically: for each field, Odoo checks whether that field is configured to keep a separate value for each company. It is not stored in the database, so it is always up to date and cannot be edited by hand.
This is mainly a developer/administrator tool. It touches the technical models ir.model.fields and ir.model, and the views that display them. No menus, buttons, emails, scheduled jobs or business rules are added.
Depends on
Models and fields (1)
- ir.model.fields · extends an existing modelcompany_dependent
Text generated by AI (DeepSeek) from reading the Odoo 14.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: 3 confirmed, 6 with no information of 9 versions.
Sources · Odoo 13.0
Confirmed on 2026-11-03 in branch 13.0 of OCA/multi-company.
terminal Installation and usage
No verified informationInstallation 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.