many2one_avatar_resource

A resource.resource can be a person or a piece of equipment. This widget renders the link to one with an avatar that reflects which, so a planning row reads at a glance rather than requiring you to know the names.

It is built with buildM2OFieldDescription, so it behaves like a normal many2one for search and selection, and adds the o_field_many2one_avatar class for styling.

To know which kind of resource it is looking at, it declares field dependencies on display_name and resource_type. A comment in the source explains the second one: a related field would have been the obvious approach, but related fields are only supported for x2many, so the dependency is declared explicitly instead.

Anywhere you schedule both people and machines, this is the widget that keeps the two visually separate. A planning board where a CNC machine and a technician look identical is a board people misread.

The thing worth deciding deliberately is whether clicking a resource should open it. On a scheduling screen, opening the resource record is usually a distraction from the task at hand, and by default Odoo agrees with that everywhere except the form view. If your users are getting pulled off a planning list into resource records, that is configurable, and the next section says how.

Standard use, with the default per-view behavior:

<field name="resource_id" widget="many2one_avatar_resource"/>

Make the resource clickable in a list, where it would not be by default:

<field name="resource_id" widget="many2one_avatar_resource"
       options="{'no_open': False}"/>

Stop it opening on a form, where it otherwise would:

<field name="resource_id" widget="many2one_avatar_resource"
       options="{'no_open': True}"/>

The whole behavior is one expression in extractProps:

canOpen: "no_open" in staticInfo.options
    ? !staticInfo.options.no_open
    : staticInfo.viewType === "form",

Read it carefully, because the two branches behave differently. If no_open is present at all, its value decides, in every view. If it is absent, the view type decides, and only a form view gets a clickable link.

Two things follow. First, this option exists and works despite appearing in no option list, no documentation and no Studio panel. It is readable only from the source. Second, the presence check is "no_open" in options rather than a truthiness test, so writing {'no_open': False} is not the same as omitting it. Omitting it in a list view gives you a non-clickable link; setting it to False in the same list gives you a clickable one.

That distinction catches people who assume False is the default. It is not. Absent is the default, and absent means something different in each view.

Odoo 20 renames this widget's kanban variant. kanban.many2one_avatar_resource is gone and card.many2one_avatar_resource takes its place.

That is not specific to this widget. Odoo 20 introduces a Card renderer, Kanban records render through it, and every one of the fourteen kanban. prefixed registrations in Odoo 19 became card.. There are zero kanban. field registrations left in Odoo 20.

The base registration, the options behavior and the field dependencies are unchanged, so an ordinary view carries over untouched. Only custom code that registered or referenced the kanban. variant needs editing.