Ensure that assets are generated and stored in the DB when Odoo starts
If the assets from the database are not up-to-date, they are regenerated by Odoo when we print a report, but to do so Odoo forces the commit, so if an exception occurs after (or during) the report rendering, it let the database in a broken state (picking have been validated in this case).
To prevent this issue, we need to ensure that the assets are well-generated when Odoo starts, not when the report is printed.
Table of contents
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
- Sébastien Alix <sebastien.alix@camptocamp.com>
- Michael Tietz (MT Software) <mtietz@mt-software.de>
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/web project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.