Skip to Content

PMIS Localization Policy

English | Slovenščina

Beta License: LGPL-3 PMISuite/mentis Version: 18.0

Start a fresh Slovenian accounting setup with the PMIS chart selected automatically. This base-only addon makes l10n_si2 the automatic Slovenian localization when its installable manifest is available on the configured addons path and the addon has been discovered in the Apps list.

Install this policy first, then install Accounting in a separate operation. For an existing upstream l10n_si database, plan a separate accounting migration before adopting the replacement.

Table of contents

Documentation

  • User Manual: illustrated two-step installation, localization checks and troubleshooting.

Features

The policy disables automatic installation of upstream l10n_si and enables l10n_si2 when Accounting is installed or scheduled and a Slovenian company exists. Odoo's country filtering continues to select other localizations for other countries. Installing the policy alone does not install Accounting or a chart. Localization modules are database-wide; accounting charts remain company-specific.

Configuration

  • The only dependency is base; automatic installation is disabled.

  • Place both the policy and replacement sources on the addons path and refresh Apps discovery before installation.

When the replacement is unavailable or its manifest is not installable, the upstream manifest's automatic-installation rules apply. Removing addon files from an installed replacement is not a supported fallback: restore the code before performing module operations.

Usage

Installation

Fresh databases require two completed installation steps:

  1. Put the policy and desired localizations on the addons path, refresh module discovery, and install l10n_pmis with only Base installed.

  2. In a subsequent installation operation, install Accounting or the desired business applications. For a Slovenian company, Odoo schedules l10n_si2.

Do not request the policy and Accounting together in the first installation batch. Odoo computes automatic dependencies before new overrides are active. Merely checking out this repository does not activate the policy.

For a database already using l10n_si2, have the administrator confirm that the installed chart provider and available sources match before adding the policy. The policy controls localization selection; it does not convert accounting entries or change payment-reference settings.

The supported existing installation has l10n_si2 installed and l10n_si uninstalled. Adoption fails if upstream is installed or scheduled while the replacement is available. Explicit upstream dependencies are not rewritten; l10n_si2 declares upstream incompatible, so conflicting installation requests fail instead of loading both charts. Existing upstream accounting requires a separate migration before adopting this replacement policy.

Data model notes

The addon updates only the two localization catalog records' auto_install, dependency auto_install_required, and manifest-derived country metadata. It uses the ORM and leaves manifest files and OCB unchanged. Requirements are refreshed after Apps-list updates and localization installation/upgrade completion, before module installation planning, and before country-based localization installation. Cached company localization candidates are invalidated when metadata changes. Repeated synchronization does not rewrite unchanged values.

The replacement keeps auto_install=False in its source manifest: automatic replacement is activated by this policy, not by discovery alone. Its Accounting extension resolves si explicitly to its own template metadata and CSV files. That extension remains active whenever l10n_si2 is installed.

Uninstalling the policy restores the current source manifests' automatic rules and dependency triggers; it does not uninstall charts or convert companies. Keep the policy installed while using automatic PMIS localization setup: restoring upstream automatic installation while retaining the replacement can cause subsequent localization requests to fail their module-exclusion check. Do not uninstall either accounting localization as a way to migrate accounting.

Bug Tracker

Bugs are tracked on PMISuite Repository Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback.

Credits

Authors

Contributors

  • Luxim d.o.o. - Matjaž Mozetič

Maintainers

LUXIM MATMOZ

Current maintainer:

sysadminmatmoz

Luxim is an independent R&D and deployment company focused on solving complex problems in the Odoo ecosystem.

Odoo Community Association

Luxim is an active member of OCA (Odoo Community Association).