Missing Field Reference
A finding from the Migration Audit that flags references to a field or model that may not exist in the target Odoo version.
What This Finding Means
The module references a field or model that was removed, renamed, or moved to the Enterprise edition in the target version. The reference may appear in Python, in a view, or in a domain expression.
Why It Matters
A reference to a field that no longer exists raises an error at view load or at ORM access time, which can block installation or upgrade. Fields that moved to Enterprise will be missing on a Community deployment even if the version number matches.
Example
order.commitment_date
Confirm that sale.order.commitment_date exists in the target version's Community edition before relying on it.
Target Version Risk
- Field removed or renamed between versions
- Field present only in Enterprise on the target version
- Model split or merged, changing the field's home
Recommended Fix Direction
Run the Field Validator to check whether the field exists on the target version and edition. If it is gone, provide a fallback field definition in your module or add a conditional code path that handles its absence.
How to Verify Manually
On a clean target database, open the model in the developer view or query ir.model.fields for the field name. Confirm it is present in the edition you plan to deploy.
Related Odoo Doctor Tool
The Field Validator checks whether the fields and models your module references exist in a chosen Odoo version and edition.
Validate Odoo Fields