Wednesday, May 8, 2024
3 changes · saas-17.2
Resolved issues and error corrections
A test setup was adjusted so the accounting bill upload screen can be checked reliably when the Indian localization is installed. This prevents false test failures and helps keep accounting features stable across localized configurations.
Original PR description
The test `can render AccountMoveUploadKanbanView` fails with l10n_in. The test does not setup the companies for the service. It causes un undefined issue in the method `qrBillScannerController`, in the module `l10n_in_qr_code_bill_scan` We will just patch the `search_read` for it (it's the easiest to patch). Linked to runbot 58753 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix ensures copied databases do not accidentally contact live external barcode lookup services. It helps support teams investigate issues safely without risking changes or customer impact from production-like duplicates.
Original PR description
This commit adds the missing neutralization necessary for the product_barcodelookup module introduced in [1] The purpose of the standard neutralization framework is to allow us to create database copies that will not interact with external systems in ways that could impact the production database (or if it is not possible to prevent the interactions, make sure that they are benign or wont result in actual changes), or impact the customers of the operator of the production database. This is mainly useful to allow safe support investigation on database duplicates. [1] https://github.com/odoo/enterprise/pull/61949
Import summary fields used only for internal counting are no longer marked for translation. This keeps translation files cleaner and avoids unnecessary localization work for labels that users never see.
Original PR description
…atable Those fields are just counting stuff, and their labels are never displayed. So it's useless having them in the .pot file