payment_term_line_ids

Odoo's editable lists have a sensible rule: a row you created but never touched is discarded when you move on. It stops a stray click on the Add a line link from leaving empty rows behind, and on most lists nobody notices it.

Payment terms are the exception. A new installment line arrives pre-filled with meaningful defaults, a percentage and a delay, and a user who adds one and then clicks on another line to compare has changed nothing. Odoo's rule then throws the row away, which looks exactly like a bug.

This widget removes the ambiguity. It intercepts the creation of a new inline row and immediately applies an empty update to it, which marks it as modified. From that moment the row is a real edit and Odoo will not discard it.

Payment terms are configured rarely and by people who are not in Odoo every day, which is exactly the audience that cannot tell the difference between a deliberate rule and a broken screen. A disappearing row on a finance configuration page generates a support ticket and, worse, a suspicion that the rest of the configuration did not save either.

The wider lesson is about defaults. Odoo's abandon rule assumes an untouched row is worthless, and that assumption breaks whenever a new row arrives with defaults that are already correct. Any custom list where a new line is useful as created has the same exposure, and this widget is the smallest fix for it.

The core usage

<field name="line_ids" widget="payment_term_line_ids"
       nolabel="1" colspan="2">
  <list editable="bottom">
    ...
  </list>
</field>

The embedded list is an ordinary editable list. All the widget changes is what happens the moment a new row appears.

Reusing it on your own list

<field name="schedule_ids" widget="payment_term_line_ids">
  <list editable="bottom">
    <field name="percentage"/>
  </list>
</field>

Nothing in the widget is payment-term specific, so any list whose new rows arrive usefully pre-filled benefits.

The standard behavior, for comparison

<field name="line_ids">
  <list editable="bottom"> ... </list>
</field>

A new row here is discarded if the user clicks away without editing it.

The entire widget is a subclass whose setup replaces one hook. The standard add-inline-record helper creates a new record in the list and hands it to the editor; this version wraps that creation so that after the record exists, an empty update is applied to it.

An empty update sounds like a no-op and is not. Odoo's record model treats any update as a modification, so the record's dirty state flips. The abandon logic that runs when focus leaves an untouched new row checks exactly that state, so the row now survives.

The source comment says as much in one sentence, and it names the two situations it protects: clicking globally, and clicking on an existing record. Both are ordinary things to do while adding an installment line, which is why the fix was needed on this form in particular.

Note what the widget does not do. It does not save anything, it does not validate the row, and it does not stop the user deleting it. The row is simply no longer eligible for silent removal, so an unwanted line has to be removed on purpose, which on a configuration form is the right default.

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, which is notable in a release cycle that rewrote most field widgets onto the new props syntax. It survives untouched because it declares no props and only replaces one hook.