field_partner_autocomplete

The widget extends the standard char field and adds an autocomplete whose suggestions come from Odoo's partner enrichment service. Selecting one fetches the full company record and writes it onto the form.

It does more than fill fields. On res.partner it saves the record, calls enrich_company_message_post so the chatter records what was enriched, and reloads the record. It then tells the model bus the form is no longer dirty.

Two details worth knowing before you place it. Suggestions are filtered by the record's country_id unless the worldwide path is used, and the logo is written to a different field depending on the model.

This is the difference between a salesperson typing an address from a business card and picking a company from a list. For a team creating new customers or vendors daily, it removes both the typing and the transcription errors that follow it.

Two things to tell the team. The enrichment service costs credits, so a habit of enriching every record including ones you already have is a real bill. And on a contact record it saves the form for you, so an enrichment cannot be undone by simply discarding the form. If someone picks the wrong company, they are editing a saved record rather than abandoning an unsaved one.

On a company name field:

<field name="name" widget="field_partner_autocomplete"/>

For country-scoped results to work, the country field has to be loaded on the form:

<field name="country_id"/>
<field name="name" widget="field_partner_autocomplete"/>

Most field widgets change what you see. This one changes the record's lifecycle, and only on res.partner:

if (this.props.record.resModel === 'res.partner') {
    const saved = await this.props.record.save();
    if (saved && data.isEnrichAccessible) {
        await this.orm.call("res.partner", "enrich_company_message_post",
                            [this.props.record.resId, additionalData]);
        this.props.record.load();
    }
}

this.props.record.model.bus.trigger("FIELD_IS_DIRTY", false);

Three consequences. The record is written to the database at selection time, so Discard no longer reverts the enrichment. The chatter gains a message describing what was enriched, which is useful for audit and surprising if you did not expect it. And the form is marked clean, so a user who navigates away gets no unsaved-changes warning even though the record just changed substantially.

On any other model none of that happens: the fields are filled and the form stays dirty like any normal edit.

The other asymmetry is the logo:

const logoField = this.props.record.resModel === 'res.partner' ? 'image_1920' : 'logo';

If you put this widget on your own model and the logo never appears, the reason is that the widget is looking for a field called logo, not image_1920. Name the field logo and it lands.

No change. Diffing the registration between the 19.0 and 20.0 branches shows the same component shape and no options added or removed.