form_page_dependencies

Deleting a page that other pages link to is how a site grows broken links, and the only way to avoid it is to know what points at the page before you act.

Odoo has a shared component that answers that question and shows the results in a popover. This widget is a version of it for a form where the identifiers are not known up front.

Instead of receiving them, it reads a target model field from the current record and asks about that. Everything else, the fetch, the popover, the cleanup, is inherited.

Internal link integrity is one of the least glamorous and most consequential parts of running a site. Broken internal links waste crawl budget, frustrate visitors and are almost never noticed by the person who caused them.

Surfacing dependencies at the moment of deletion is the cheapest possible intervention. It is worth pairing with a redirect policy, because knowing what links to a page only helps if there is an agreed answer for what to do about it.

Placing it

<widget name="form_page_dependencies"
        resModel="ir.model"
        mode="link"/>

The extractor reads these attributes directly.

How targets are resolved

# read target_model_id from the current record
# and ask about that, not about the record

The overridden method, and the only difference.

The base component

# takes resIds as a required prop

Used where the identifiers are already known.

The subclass is fifteen lines and overrides one method: the one that supplies the identifiers to ask about.

The base returns whatever was passed in as a prop. This version reads the current record, pulls a target model field from it and returns the identifiers that field points at. So on a form describing a relationship to a model, the dependencies shown are the model's, not the form record's.

Everything downstream is inherited: a single server call collecting URL dependencies for those targets, the popover that displays them, and the careful teardown that waits for the popover's hide event before disposing it.

The extractor is the other notable thing. Most view widgets take only the standard props; this one reads four attributes from the element, defaulting the name to an empty string so an omitted attribute does not surface as undefined. That is what lets the same component serve different models and display modes from view XML.

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 this page after the release.

Byte-identical. The subclass, its optional identifiers prop and its extractor match Odoo 19 exactly on the development branch.