PaymentWizardCopyClipboardButtonField

Odoo's payment link wizard generates a URL a customer can pay through. The URL depends on the amount, the partner and a signature, so every time one of those changes the server regenerates it. That regeneration is a round trip, and while it is in flight the field still holds the old link.

The wizard's whole purpose is that you copy that link and send it, so copying the wrong one is not a cosmetic bug. A user who adjusts the amount and immediately clicks Copy would, with the standard copy button, put the previous link on the clipboard and never know.

This widget prevents that. It is the standard copy button with one change: before copying, it waits for the record model to finish whatever operation is pending. If nothing is pending it copies immediately; if a regeneration is in flight it waits for it, then copies the current value.

The failure this prevents is expensive precisely because it is invisible. A customer receives a link for the wrong amount, or a link that no longer validates, and the first symptom is a failed payment and a support conversation. Nobody suspects the Copy button.

The pattern generalizes to any field whose value is generated server side and copied by the user: signed URLs, tokens, generated references, invitation links. Wherever the value can change under the user's hand, a copy button should wait for the model rather than reading whatever is on screen.

It is also a good reminder that asynchronous recomputation is invisible in the interface. There is no spinner on a field being recalculated, so the only defense is code that knows to wait.

The core usage

<field name="link"
       widget="PaymentWizardCopyClipboardButtonField"/>

Note the CamelCase name, which is unusual in Odoo and has to be written exactly as shown.

Reusing it on a generated value

<field name="share_url"
       widget="PaymentWizardCopyClipboardButtonField"/>

Nothing in it is payment-specific. Any field recomputed by the server on change benefits from the wait.

The plain copy button

<field name="reference" widget="CopyClipboardButton"/>

Correct for a stored value that does not change while the user is looking at it.

There are two small classes. The first extends the shared copy button and overrides its click handler to await the model's operation lock before delegating to the parent. That lock is the same mechanism the record model uses to serialize its own operations, so awaiting it means waiting for exactly the pending work and no longer.

The second extends the copy clipboard field to use that button, and adds a full width class to whatever class name the parent computed. That is presentation only, and it is what makes the button span the wizard's column rather than sitting at its natural width.

The registered name is worth a note of its own. Odoo widget names are conventionally snake case; this one is CamelCase, matching the shared copy widgets it builds on, which are also registered in CamelCase. It has to be written exactly, because widget lookup is a plain string match, and a snake case guess will silently fall back to the field's type.

Between Odoo 18 and Odoo 19 the widget lost a small extractor that forwarded the field's label into the props. The button now takes its label from the parent's own handling, which is one less thing to keep in step.

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

Byte-identical. The file on the development branch matches Odoo 19 exactly, including the wait on the model lock and the full width class. Nothing about this widget changes in Odoo 20.