Partner Stage - Display only confirmed partners
Automatic filtering of partners in form views' Many2one fields with relation to "res.partner". If enabled (which is the default behavior when the module is installed), only confirmed partners will be shown.
auto_awesome What this module does
AI-generated from the code · Odoo 17.0When this module is installed, partner fields on forms only show confirmed partners by default. You can turn this filtering off per screen or globally with a system setting.
This module works together with the partner stage feature. It changes how partner selection fields behave on form screens.
- On any form, every field that links to a partner (
res.partner) is automatically limited to partners whose stage is confirmed. This applies to all models, not just one screen. - If a field already had its own filter, the confirmed-partner condition is added to it, so both rules apply together.
- The filtering is on by default when the module is installed.
- You can switch it off for a specific screen by passing a context value, or globally by setting the system parameter
partner_stage.only_confirmed_partnersto a false-like value such as False, false, empty, or 0. - The module does not add menus, buttons, or reports. It only adjusts the partner search filters used by form views.
- It touches the base view-building mechanism (
basemodel) and relies on the partner stage module for the confirmed state.
Depends on
Models and fields (1)
- base · extends an existing model
Text generated by AI (DeepSeek) from reading the Odoo 17.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 17.0
Confirmed on 2026-11-03 in branch 17.0 of OCA/partner-contact.
terminal Installation and usage
OCA documentation · Odoo 17.0Usage
Source · Odoo 17.0See "Configuration".
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.