Skip to Content
Odoo model · Enterprise

data_cleaning.rule

Cleaning Rule. Defined in module data_cleaning; exists in Odoo 18, 19, 20. Across the upgrade steps we tracked: 0 fields added, 0 removed, 0 renamed.

  1. Odoo 16 not covered
  2. Odoo 17 not covered
  3. Odoo 18 data_cleaning
  4. Odoo 19 data_cleaning
  5. Odoo 20 data_cleaning

This is an Enterprise model: Odoo 16 and 17 Enterprise sources are not part of the data, so those versions show as not covered.

Odoo 17 to 18

Community only All changes in this step

Not covered: this step compares Community modules only and this model belongs to an Enterprise module.

Odoo 18 to 19

Community + Enterprise All changes in this step

No change to this model's own fields in this step.

Odoo 19 to 20

Community + Enterprise All changes in this step

No change to this model's own fields in this step.

All fields declared on data_cleaning.rule (11)

Fields this model declares itself in any version, with the versions they exist in. Inherited fields (mail.thread and other mixins) are on the parent model's page.

present not present not covered (Enterprise, Odoo 16 and 17)

Show all 11 fields
FieldTypeLabelModule1617181920
actionselectionActiondata_cleaningE
action_caseselectionCasedata_cleaningE
action_displaychardata_cleaningE
action_technicalchardata_cleaningE
action_trimselectionTrimdata_cleaningE
cleaning_model_idmany2one data_cleaning.modelCleaning Modeldata_cleaningE
field_idmany2one ir.model.fieldsFielddata_cleaningE
namechardata_cleaningE
res_model_idmany2onedata_cleaningE
res_model_namecharModel Namedata_cleaningE
sequenceintegerSequencedata_cleaningE

Related models

Linked by its relational fields: data_cleaning.modelir.model.fields

Coverage. Odoo 16 to 17 and 17 to 18 compare Community modules only (the Enterprise 16 and 17 sources are not available to us). Odoo 18 to 19 and 19 to 20 include Community and Enterprise modules. Everything here comes from a static read of the Odoo source code: a field counts as removed only when no parent model, mixin or delegated model still provides it. Fields created dynamically at run time can be missed, and entries we could not confirm are marked as low confidence.