google_address_autocomplete

The widget extends the standard char field and replaces its input with an autocomplete backed by Google Places. Picking a suggestion calls back for the full address detail, then writes every part of it onto the record in one update.

Seven address parts are handled: street, street2, city, state_id, zip, country_id and city_id. Each is exposed as an option so you can name the field it writes to, which is what lets the widget work on a model that is not res.partner.

Many2one parts are written as proper record references rather than text. The code checks the field type and builds { id, display_name } when the target is a many2one, so country and state land as real links.

Address typos are the quiet tax on any Odoo database that ships things or invoices across borders. This widget removes most of them by making the address come from Google rather than from a keyboard.

There are two costs to weigh. It sends what the user types to Google, which matters if your addresses are sensitive or your organization has data-residency commitments. And it needs an API key, which means a bill that scales with use and an account someone has to own.

For a sales or delivery team entering addresses all day, it pays for itself. For a model where addresses are typed twice a month, it usually does not.

On res.partner, where the field names already match, no options are needed:

<field name="street" widget="google_address_autocomplete"/>

On a model with its own naming, map each part and make sure every mapped field is in the view:

<field name="delivery_street" widget="google_address_autocomplete"
       options="{'street': 'delivery_street', 'city': 'delivery_city',
                 'zip': 'delivery_zip', 'country_id': 'delivery_country_id'}"/>
<field name="delivery_city"/>
<field name="delivery_zip"/>
<field name="delivery_country_id"/>

The update loop checks the view before it writes:

const recordFieldName = addressFieldMap[fieldName] || fieldName;
if (recordFieldName in activeFields) {
    ...
    valuesToUpdate[recordFieldName] = value || false;
} else if (!(recordFieldName in fields) && value) {
    ...
}

activeFields is what the view actually loaded. A field that exists on the model but is not placed in the form is not in that set, so the widget skips it. No error, no console warning, no partial save. The user picks an address, most of it lands, and one box stays empty.

This is the single most common complaint about this widget, and the fix is always the same: put the field in the view. It can carry invisible="1" if users should not see it. It just has to be loaded.

The second half of that branch explains a stranger symptom. Address parts that correspond to no field at all are collected and, at the end, joined into the widget's own field:

if (!(this.props.name in valuesToUpdate) && rest.length) {
    valuesToUpdate[this.props.name] = rest.join(" ");
}

So a half-configured widget does not silently lose the city and the zip. It stuffs them into the street line. If your street field keeps filling with a whole address run together, that is this branch firing, and it means your mapping is incomplete rather than wrong.

No change. Diffing the registration between the 19.0 and 20.0 branches shows no options added or removed and no change to the supported type.

The seven mapping options are generated from a single table in the source rather than written out one by one, so they move together if Odoo ever adds an eighth address part.