Skip to Content
Odoo model

calendar.popover.delete.wizard

Calendar Popover Delete Wizard. Defined in module calendar; exists in Odoo 17, 18, 19. Across the upgrade steps we tracked: 2 fields added, 1 removed, 0 renamed.

  1. Odoo 16 not present
  2. Odoo 17 calendar
  3. Odoo 18 calendar
  4. Odoo 19 calendar
  5. Odoo 20 not present

Odoo 16 to 17

Community only All changes in this step

New model in Odoo 17.

Odoo 17 to 18

Community only All changes in this step

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

Odoo 18 to 19

Community + Enterprise All changes in this step

Fields removed (1)

FieldTypeModuleNotes
recordmany2onecalendar

Fields added (2)

FieldTypeModule
calendar_event_idmany2onecalendar
recipient_idsmany2manycalendar

Now also inherits mail.composer.mixin (fields from these parents are listed on their own pages).

Odoo 19 to 20

Community + Enterprise All changes in this step

Removed in Odoo 20.

2 views of this model removed
  • calendar.calendar_popover_delete_view
  • calendar.view_event_delete_wizard_form
1 actions on this model removed
  • calendar.action_event_delete_wizard

All fields declared on calendar.popover.delete.wizard (4)

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 4 fields
FieldTypeLabelModule1617181920
calendar_event_idmany2one calendar.eventCalendar Eventcalendar
deleteselectioncalendar
recipient_idsmany2many res.partnerRecipientscalendar
recordmany2one calendar.eventCalendar Eventcalendar

Related models

Inherits: mail.composer.mixin

Linked by its relational fields: calendar.eventres.partner

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.