Skip to Content
Odoo model

calendar.provider.config

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

  1. Odoo 16 calendar
  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

Fields added (2)

FieldTypeModule
cal_sync_pausedbooleancalendar
microsoft_outlook_sync_pausedbooleancalendar

Odoo 17 to 18

Community only All changes in this step
1 actions on this model removed
  • calendar.action_view_start_calendar_sync

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

Removed in Odoo 20.

1 views of this model removed
  • calendar.calendar_provider_config_view_form

All fields declared on calendar.provider.config (7)

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 7 fields
FieldTypeLabelModule1617181920
cal_client_idcharGoogle Client_idcalendar
cal_client_secretcharGoogle Client_keycalendar
cal_sync_pausedbooleanGoogle Synchronization Pausedcalendar
external_calendar_providerselectionChoose an external calendar to configurecalendar
microsoft_outlook_client_identifiercharOutlook Client Idcalendar
microsoft_outlook_client_secretcharOutlook Client Secretcalendar
microsoft_outlook_sync_pausedbooleanOutlook Synchronization Pausedcalendar
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.