PMIS Audit upgrade guide
Module overview · English manual · Slovenian manual
A source update and restart do not install the addon's models, menus, views, and access rights. The deployment owner must perform the module upgrade using the normal controlled deployment process.
Coordinate installed compatibility modules
If pmis_audit_server_actions is installed, keep the sibling temporary
repository available in addons_path and upgrade pmis_ux, pmis_audit, and
pmis_audit_server_actions together. The compatibility module retains its
technical name for existing dependencies. Follow its
coordinated upgrade notes.
Legacy views during an upgrade
The pre-migration in migrations/18.0.1.2.1/pre-migration.py deactivates four
known obsolete child views when applicable:
pmis_audit_server_actions.pmis_stock_valuation_layer_formpmis_audit_server_actions.pmis_stock_valuation_layer_treepmis_audit.view_move_line_form_auditpmis_audit.view_move_line_tree_audit
These views reference retired valuation overrides or landed-cost snapshot fields. The migration archives matching views before this addon loads its parent views. It preserves business data and retains the records and XML IDs for normal cleanup when the owning addons are upgraded. Missing or already inactive views require no changes.
During a full upgrade, another addon can validate shared journal-item views
before Odoo reaches this addon's pre-migration. If that validation fails because
of the obsolete pmis_audit.view_move_line_form_audit or
pmis_audit.view_move_line_tree_audit view, have the deployment owner deactivate
those specific views through the normal administrative process before retrying
the coordinated upgrade. The migration accepts this prior cleanup. Do not
archive unrelated views or remove business records to bypass validation.
After deployment, use the manuals for access setup and the current inventory reconciliation and correction workflows.