Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

l10n_it_vat_statement_communication update multi company rule #4354

Open
1 task
patrickt-oforce opened this issue Sep 5, 2024 · 0 comments · May be fixed by #4353
Open
1 task

l10n_it_vat_statement_communication update multi company rule #4354

patrickt-oforce opened this issue Sep 5, 2024 · 0 comments · May be fixed by #4353

Comments

@patrickt-oforce
Copy link
Contributor

patrickt-oforce commented Sep 5, 2024

When module is updated during migration not rewrite the multicompany rule

Module

l10n_it_vat_statement_communication

Describe the bug

After module migration multi company rule is updated as defined in security.xml file

To Reproduce

Affected versions:

Steps to reproduce the behavior:

  1. Create new vat communication on a migrated db
  2. Save new communication
  3. Multi company access exception is raised

Expected behavior
Exception not raised when new vat statement communication is saved on a migrated db

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants