upgrade_boolean

Open Settings on a Community database, tick something like a payroll or sign feature, and instead of enabling it Odoo shows an upgrade dialog. That behavior is not scattered logic; it is one widget on those checkboxes.

The implementation, verbatim from the source, is a boolean field with one overridden change handler. At setup it reads odoo.info.isEnterprise. On Enterprise, changes pass straight through to normal boolean behavior. On Community, the change opens UpgradeDialog, and the dialog's close handler updates the field back to false. The revert is the detail people miss: the checkbox is not blocked, it is undone, so the setting genuinely never persists as enabled on Community.

For a business evaluating Odoo, this widget is the visible boundary between the editions, drawn feature by feature right in Settings. Everything behind an upgrade checkbox works only on Enterprise (or odoo.sh/Online), which makes a Community settings page an honest inventory of what the free edition does not include.

Two practical readings. If you run Community deliberately, these checkboxes are your roadmap of what an Enterprise migration would unlock, worth reviewing annually as your needs grow. And if a team reports "the setting will not stay on", check whether it is one of these before debugging anything; the revert-on-close is designed behavior, not a bug.

Custom modules can reuse the widget for their own edition gating, though most partner modules manage licensing differently.

How core settings use it

<setting>
    <field name="module_hr_payroll" widget="upgrade_boolean"/>
</setting>

On Enterprise the tick installs the module as usual; on Community it opens the upgrade dialog and reverts.

Gating a custom Enterprise-only feature

<field name="module_my_enterprise_addon"
       widget="upgrade_boolean"/>

Legal in your own settings blocks; you inherit the exact core behavior, dialog and revert included.

The three-line revert deserves its own spotlight because it explains every observed symptom: the dialog's onClose callback runs record.update({ field: false }).

Consequences, all verified by the flow. The checkbox visibly ticks for the moment the dialog is open, then unticks, so screen recordings of "it flickers off" are the design working. Nothing is written to the database at any point, because settings only persist on Save and the value is already false again. And automations watching config values never fire, since no change survives.

The companion file, upgrade_dialog.js, renders the actual popup with its trial and upgrade links; the widget just opens it. Custom rebranding of that dialog is a separate patch on the dialog component, not on this field.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The changes below are read from the public development branch and are not final until release.

Nothing changes for this widget. Same edition check, same dialog, same revert. We re-verify once Odoo 20 ships.