OdooWiki OCA HUB

Web - Merge Notebook Tabs

web_merge_notebook_tab folder_open OCA/web open_in_new
Extra Tools License: AGPL-3

This module extend the Odoo Community Edition web module to improve display of Form views that contains notebooks.

Odoo is very modular, that is great, but for some Forms, Odoo designs the view with a lot of tabs in a notebook, one per functional topic.

If many modules are installed, it generates a lot of tabs. Consequently:

  • it force users to click a lot of time in all the tabs, to configure all the data.
  • it is not possible for a user to see quickly, if an item is correctly configured.

It is specially problematic for product or partner form views.

This module allows to 'merge' many tabs into a single tab, to avoid such UX troubles.

Demo exemple with the form view of the product.template model:

Without the module

With the module

auto_awesome What this module does

AI-generated from the code · Odoo 16.0

Lets administrators merge several tabs of a form's notebook into one single tab, so users see all the related fields together instead of clicking through many tabs.

This module adds a configuration screen where you decide, for a given form view, which existing tabs should be combined into one new tab.

  • You pick the model and the form view, give the new tab a title, and list the technical names of the tabs to merge (comma-separated).
  • You can also choose after which existing tab the new merged tab should appear; leave it empty to put it first.
  • The screen shows the list of available tab names for the chosen view, so you know what can be merged.
  • The system validates your entries: the new tab name must be a single word, the list of tabs to merge must be correctly formatted, and every tab name you mention must really exist in that view.
  • When a form is opened, the module rebuilds the view on the fly: it creates the new tab, moves the contents of the selected tabs into it (grouped by their original titles), and removes the old tabs.
  • Fields moved into the merged tab are displayed without their own label and use the full width, and nested groups also take the full width.
  • The configuration is stored in ir.ui.view.merge.notebook.tab; changes take effect immediately because view caches are cleared on create, update and delete.
  • Access is read-only for regular users and full management for ERP managers.
  • The menu entry appears under the Settings area.

Depends on

web

Menus it adds

menu_ir_ui_view_merge_notebook_tab
Models and fields (2)
  • base · extends an existing model
  • ir.ui.view.merge.notebook.tab · new modelmodel (Model Name), view_id, model_id, tab_name, tab_string, view_xml_id (View XML ID), merge_tab_names, tab_name_position, tab_names_available

Text generated by AI (DeepSeek) from reading the Odoo 16.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-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

terminal Installation and usage

OCA documentation · Odoo 16.0

Configuration

Source · Odoo 16.0
  • Go to "Settings > Technical > User Interface > Merge Notebook tab Settings"
  • Create a new setting:
  • Select the model of the view you want to change
  • Select the view you want to change
  • Set the description of the tab, that will be displayed to the user. (string parameter)
  • (optionaly) Set the name of the tab, that will be used technically. (name parameter). If not set, it will be generated automatically.
  • (optionaly) Set the name of the tab, where the new tab will be inserted. (tab_name_position parameter). If not set, the tab will be inserted at the first position.
  • set the names of the tabs you want to merge, as a python list.

No verified information in OCA: Installation, Usage.

info

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.