Skip to Content
Odoo model · Enterprise

databases.synchronization.wizard

Database Synchronization Wizard. Defined in module databases; exists in Odoo 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 not present
  4. Odoo 19 databases
  5. Odoo 20 databases

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 18 to 19

Community + Enterprise All changes in this step

New model in Odoo 19.

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 databases.synchronization.wizard (8)

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 8 fields
FieldTypeLabelModule1617181920
created_database_idsmany2many project.projectdatabasesE
database_idsmany2many project.projectdatabasesE
error_messagechardatabasesE
fetched_valuesjsondatabasesE
new_propertiesjsonNew KPIs to add:databasesE
notify_userbooleandatabasesE
property_definitionjsondatabasesE
summary_messagechardatabasesE

Related models

Linked by its relational fields: project.project

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.