Skip to Content
Odoo model · Enterprise

sale.temporal.recurrence

Sale temporal Recurrence. Defined in module sale_renting; exists in Odoo 18, 19. Across the upgrade steps we tracked: 4 fields added, 0 removed, 0 renamed.

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

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

Fields added (4)

FieldTypeModule
displayed_unitselectionsale_renting
overnightbooleansale_renting
pickup_timefloatsale_renting
return_timefloatsale_renting

Odoo 19 to 20

Community + Enterprise All changes in this step

Removed in Odoo 20.

2 views of this model removed
  • sale_renting.sale_temporal_recurrence_view_form
  • sale_renting.sale_temporal_recurrence_view_tree
1 actions on this model removed
  • sale_renting.sale_temporal_recurrence_action
1 menus opening this model removed
  • sale_renting.menu_sale_renting_periods

All fields declared on sale.temporal.recurrence (9)

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 9 fields
FieldTypeLabelModule1617181920
activebooleansale_rentingE
displayed_unitselectionsale_rentingE
durationintegersale_rentingE
duration_displaycharsale_rentingE
namecharsale_rentingE
overnightbooleanOvernightsale_rentingE
pickup_timefloatCheck-insale_rentingE
return_timefloatCheck-outsale_rentingE
unitselectionsale_rentingE
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.