This module provides a way to trigger reload of the current window on ActionManager
auto_awesome What this module does
AI-generated from the code · Odoo 15.0Adds a new action type that reloads the current view when triggered. Developers can use it in buttons or automated actions to refresh the screen without navigating away.
This module introduces a new action type called ir.actions.act_view_reload. When this action is executed, it tells Odoo to reload the currently displayed view (for example, a list or form view) instead of opening a new window or performing another action.
- It works behind the scenes: there is no new menu or button added by the module itself. Instead, it provides a building block that other modules or customizations can use.
- The action is handled by the web client: when the action is triggered, the current view is refreshed, keeping the user on the same screen but with up-to-date data.
- The module only defines the action type and its handling; it does not add any business logic, fields, or automatic rules.
- It depends on the standard
webmodule and is installed as a technical component.
This is useful for developers who want to force a view refresh after some operation, such as after a button click that changes data, without requiring the user to manually reload the page.
Depends on
Models and fields (1)
- ir.actions.act_view_reload · new model
Text generated by AI (DeepSeek) from reading the Odoo 15.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: 4 confirmed, 5 with no information of 9 versions.
Sources · Odoo 15.0
Confirmed on 2026-11-03 in branch 15.0 of OCA/web.
terminal Installation and usage
OCA documentation · Odoo 15.0Usage
Source · Odoo 15.0To use this functionality you need to return following action:
def foo(self):
self.ensure_one()
return {
'type': 'ir.actions.act_view_reload',
}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.