open_decimal_precision_button

Odoo has two different things that look like the same setting. A currency has a rounding, which controls how amounts in that currency are rounded. The database has a decimal precision configuration, which controls how many decimals amounts carry everywhere. People who want the second one very often start editing the first.

The currency form catches that. When a user starts changing the rounding it shows a warning panel explaining that decimals are a database wide setting affecting invoices, taxes and reports, and offers a way through to the right screen. This widget is that way through.

It is registered as a field widget, but it renders a button and reads nothing. The field it is attached to exists only so the panel can be shown or hidden by an ordinary invisible expression. Clicking the button discards the currency record and opens the decimal precision settings.

The order of operations is what makes this worth a page. The button discards before it navigates, which means the half-made rounding change is thrown away rather than left pending in a form the user has now walked away from. Without that, a user could return later, press save out of habit, and change a currency's rounding they had already decided not to change.

Changing decimal precision on a live database is one of the genuinely dangerous settings in Odoo. It affects stored amounts across every model, and lowering it after data exists loses information. The panel exists to slow that decision down, and the widget exists to make sure the detour does not leave a mess behind it.

The core usage

<div>
  <p>You are changing decimals in your entire database,
     including invoices, tax amounts, accounting amounts,
     reports. This is probably not intended.</p>
  <field name="display_rounding_warning"
         widget="open_decimal_precision_button"/>
</div>

The field carries no meaning of its own here; the surrounding panel is shown or hidden by the record's warning flag.

Controlling when the button appears

<div invisible="not display_rounding_warning">
  <field name="display_rounding_warning"
         widget="open_decimal_precision_button"/>
</div>

Standard visibility handling. The widget itself has no conditional logic.

What it does on click

# in order:
await record.discard()          # unsaved changes are dropped
action.doAction("base.action_decimal_precision_form")

The discard is awaited before the action opens, so the form is clean by the time the user leaves it.

There are only two things to say about this widget, and both are about what it is not.

It is not a field. Its props are the standard field props, but the component never reads the record's value for its own field. It uses the record only to call discard on it. That makes the field name it is attached to a placeholder, which is why core points it at the boolean that governs the warning panel's visibility.

It is not a view button either, even though that is what it looks like. A view button with a type of object or action would run through Odoo's button pipeline, which saves the record before executing. That is precisely the wrong behavior here: saving is the thing the panel is trying to prevent. Registering a field widget instead is what lets the click discard rather than save.

Everything else is one line each. The component takes the action service in setup, and the handler awaits the record discard, then opens the settings action by its external identifier. There is no confirmation dialog, so a user who clicks it loses the current edit without being asked, which is intentional given that the panel exists to stop that edit.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this can still change; we re-verify the page after release.

Byte-identical. The file on the development branch matches Odoo 19 exactly. The discard, the hardcoded action and the absence of options are all unchanged.