Skip to Content
Odoo model · Enterprise

calendar.booking.line

Meeting User/Resource Booking. Defined in module appointment_account_payment; exists in Odoo 18, 19, 20. Across the upgrade steps we tracked: 1 fields added, 0 removed, 0 renamed.

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

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 (1)

FieldTypeModule
appointment_user_idmany2oneappointment_account_payment

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 calendar.booking.line (5)

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 5 fields
FieldTypeLabelModule1617181920
appointment_resource_idmany2one appointment.resourceResourceappointment_account_paymentE
appointment_user_idmany2one res.usersUsersappointment_account_paymentE
calendar_booking_idmany2one calendar.bookingMeeting Bookingappointment_account_paymentE
capacity_reservedintegerCapacity Reservedappointment_account_paymentE
capacity_usedintegerCapacity Usedappointment_account_paymentE

Related models

Linked by its relational fields: appointment.resourcecalendar.bookingres.users

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.