Technical
Lynx Accounting (former name, compatibility)
Renamed to lynx_accounting: upgrading this module moves a database to the new name
lynx_accounting_enterprise
· v19.0.4.0.0
· Standard
What this solves
lynx_accounting_enterprise is now lynx_accounting
This module was renamed lynx_accounting in 19.0.4.0.0. What remains under the old name is this empty compatibility module. It holds no models and no data; its only content is a dependency on lynx_accounting.
What happens on upgrade. Upgrading this module (odoo -u lynx_accounting_enterprise, -u all, the Kubernetes migration job or lynx-up.sh --update) makes Odoo install lynx_accounting, which adopts everything the old module owned before loading its own data: records, external ids, settings, menus and access rights. Nothing is recreated or deleted.
Do not skip the upgrade. A tenant that only restarts on the new code, without upgrading, keeps its data but has no Accounting menus until it is upgraded.
Do not uninstall this module before the upgrade has run, and never on a database that has not been upgraded: on such a database it still owns every accounting record. Once every tenant runs lynx_accounting, this module can be uninstalled and dropped from the code.
New databases install lynx_accounting directly and never need this module.
Depends on
Try Lynx Accounting (former name, compatibility) on your team.
Free trial, no credit card. Talk to sales when you're ready.