Thursday, April 30, 2026
5 changes · 17.0
Enhancements to existing features
This update ensures the ‘pos_blackbox_be’ module works seamlessly with the latest Odoo images used for IoT Boxes. It backports a previous fix to maintain compatibility and improve the functionality of these devices within the Odoo Enterprise system.
Original PR description
Backport of #100440 opw-6172860
Resolved issues and error corrections
This update fixes a potential error in the Danish tax reporting module that could cause unexpected application crashes. The issue stemmed from a mismatch between how error messages were handled and the expected data type, specifically related to string formatting. The fix includes added tests and resolves the problem, ensuring more stable reporting.
Original PR description
before this commit, if the SKU server was returning an error message, the error handler would raise an exception because of the lazyTranslate. The reason is that `join()` expects an actual sting as argument, not a lazy string. This commit adds some tests for the error case and fixes the error due to the lazytranslate in the error codes. opw-6171466
A bug preventing list view editing within Studio mode has been resolved. The issue stemmed from an incorrect domain check related to company IDs, which wasn't properly handled due to the view's structure. Adding hidden fields to the XML view resolved the conflict and restored the ability to edit list views.
Original PR description
Steps to reproduce:
1. Install Invoicing and Studio
2. Go the Journal Entries list view
3. Enter Studio mode
4. Go to View, and Enable Mass Editing
The following traceback is raised:
```py
Field 'company_id' used in domain of python field 'journal_id' (
(company_id and ['|', ('company_id', '=', False), ('company_id', 'parent_of', [company_id])] or ['|', ('company_id', '=', False), ('company_id', 'parent_of', [''])]) + ([('id', 'in', suitable_journal_ids)])) is restricted to the group(s) base.group_multi_company.
```
Now that the list view is editable, there is a check being performed on the `journal_id`'s company and domain. However, those fields aren't present in the view, thus OWL is unaware of their values and cannot properly apply the `journal_id`'s check_company, nor domain. By adding those two fields as `column_invisible`, the error is fixed.
Ticket [link](https://www.odoo.com/odoo/project.task/6119955)
opw-6119955This update addresses a limitation in how Odoo updates its product UNSPSC codes. Previously, new codes could only be added during initial module installation. Now, a new upgrade script automatically adds updated codes to the database, ensuring our product data remains current with industry standards. Existing product codes are not modified.
Original PR description
**Problem:** Periodically, the UNSPSC codes may be updated and they must be added to existing databases. Normally this is done by module update, however, since there are thousands of UNSPSC codes, a CSV imported via SQL is used instead of XML files. This import is only implemented on module install and not module update, so there is no way to update the UNSPSC codes in existing databases. **Solution:** An upgrade script based on the post-init hook has been added, which will add the new codes to the database, if any. Note that: - The version of this upgrade script should be bumped any time the codes list is updated. - Existing records will not be updated opw-5943366
This update adds logging of Amazon request IDs from the SP-API responses. Previously, these IDs were missing, making it harder for support teams to troubleshoot issues with Amazon integrations. This change improves support efficiency and reduces investigation times.
Original PR description
Each response from Amazon's SP-API includes a request identifier used by their support team for debugging. This identifier was not previously logged, making support investigations more difficult.