Task 20 of Phase 0: document the sub-module split. - fusion_accounting_core: foundation doc covering security groups, shared-field schema preservation, and the Enterprise-detection helper. - fusion_accounting_ai: preserves the original module's AI-specific design decisions, Odoo 19 gotchas, deployment commands, controllers, models, theme rules, and known issues. Adds a new Data-adapter pattern section documenting tri-mode routing (fusion / enterprise / community). - fusion_accounting_migration: doc for the Enterprise uninstall safety guard and the wizard shell that future feature sub-modules will extend. - fusion_accounting (meta): rewritten CLAUDE.md as a pure overview pointing at sub-modules, plus a new README.md covering one-click install/uninstall. Each sub-module now has CLAUDE.md (Cursor/Claude context), UPGRADE_NOTES.md (version-by-version deltas / reference sources), and README.md (user-facing install/usage docs). 11 files total. Made-with: Cursor
1.7 KiB
Fusion Accounting Core
Foundation module for the Fusion Accounting suite.
What it does
- Defines three security groups: Fusion Accounting User / Manager / Administrator
- Auto-promotes Odoo
account.group_account_user-> Fusion User andaccount.group_account_manager-> Fusion Admin - Declares schema-preservation fields on
account.moveandaccount.reconcile.modelso that Enterprise extension fields (deferred revenue links, signing user, etc.) survive an Enterprise uninstall - Exposes the helper
env['ir.module.module']._fusion_is_enterprise_accounting_installed()
Install
This module never installs alone. Install fusion_accounting (the meta-module)
or any of the feature sub-modules — they all depend on fusion_accounting_core.
Uninstall
Uninstalling fusion_accounting_core will remove the security groups and the
schema-preservation fields. If Enterprise is also installed, uninstalling
fusion_accounting_core will cause Odoo to consider the deferred / signing
fields owned only by Enterprise — which is the original Enterprise-only state
(no data loss, just back to Enterprise-controlled schema).
Troubleshooting
If users are missing the "Fusion Accounting" privilege section in user settings
after install, the implied_ids mechanism only fires for newly-added users.
Backfill existing users via SQL:
INSERT INTO res_groups_users_rel (gid, uid)
SELECT g.res_id, gu.uid
FROM res_groups_users_rel gu
JOIN ir_model_data g ON g.module = 'fusion_accounting_core' AND g.name = 'group_fusion_accounting_user'
JOIN ir_model_data ag ON ag.module = 'account' AND ag.name = 'group_account_user' AND gu.gid = ag.res_id
ON CONFLICT DO NOTHING;