Daily updates from Odoo
Saturday, April 4, 2026
6 changes · master
New functionality added to Odoo
This update adds a visual icon for the Lazada module within Odoo. This improves the user experience by clearly identifying the Lazada integration and making it easier to find within the application's navigation.
Original PR description
Add Lazada icon to the module Forward-Port-Of: odoo/enterprise#105010
Resolved issues and error corrections
This update resolves a bug in the account reports testing environment. The fix addresses inconsistencies in data handling and ensures report lines correctly display invoice references. This improves the reliability of test results and the accuracy of account reporting.
Original PR description
Now that context is not hacked, some flush and write are done a bit differently. Fix tests. account_reports: probably due to a missing flush or data computation tests were a bit hacked to account for invalid data. This is now fixed, report line correctly contains the invoice reference.
This update prevents the system from incorrectly syncing ‘e-Cobranza’ documents (collection notes) as vendor bills in the Uruguayan localization. This change aligns with how we handle other related documents like ‘e-Remito’ and ‘e-Resguardos’, ensuring data consistency and accuracy for vendor billing.
Original PR description
This pull request improves the synchronization process of vendor bills within the Uruguayan localization (`l10n_uy_edi`). Currently, the system might fetch documents that are not technically bills during synchronization. With this change, the system will explicitly avoid synchronizing `e-Cobranza` (Collection notes or Receipts) documents as vendor bills. Reasoning: `e-Cobranza` documents function conceptually more like payment receipts rather than actual vendor bills. Pulling them into the system as bills creates inconsistencies. This update aligns the handling of `e-Cobranza` with the existing behavior for `e-Remito` (Delivery Guides) and `e-Resguardos` (Withholdings), which are also appropriately excluded from bill synchronization. **Related Tasks** LATAM Task: 1367 ADHOC Task: 58906 Forward-Port-Of: odoo/enterprise#100549
This update resolves an issue where the 'Edit Properties' button was unexpectedly appearing in the project dashboard. The fix prevents the button from showing up when it's not relevant, streamlining the user experience for project management. This ensures users only see options that apply to their current project setup.
Original PR description
Steps to produce: --- - Install `Databases` modules. - Go to project > Switch to list view and open project. - Click on the gear icon > Click `Edit Properties.` Observation: --- - Clicking `Edit…
Steps to produce: --- - Install `Databases` modules. - Go to project > Switch to list view and open project. - Click on the gear icon > Click `Edit Properties.` Observation: --- - Clicking `Edit Properties` does nothing. Root cause: --- - The `Edit Properties` action appears whenever a properties field is present in the view. - Currently, in `project.project` the field `database_kpi_properties` is added from database module (See [1]). - Here at [2], the field is added in `edit_project` view. - However, the field is only visible when `database_hosting` is set, and its value is different from `other`. Solution: --- - Patched `FormController.getStaticActionMenuItems()` and added a condition to make the `addPropertyFieldValue` menu item unavailable when the current model is `project.project`. [1]: https://github.com/odoo/enterprise/blob/84022deef3414096fcaf61f8d45c08393431e0ab/databases/models/project_project.py#L36 [2]: https://github.com/odoo/enterprise/blob/84022deef3414096fcaf61f8d45c08393431e0ab/databases/views/databases_project_views.xml#L158 Note: --- - Also found that, clicking `Edit Properties` from a page other than the KPI page does nothing. We could either show a guiding `dialog box` or limit the visibility of `Edit Properties` to the KPI page only. opw-5933007 --- Forward-Port-Of: odoo/enterprise#108056
This update fixes an error preventing Intervat from properly verifying our connections. The issue stemmed from outdated JWK keys being archived on IAP, which caused authentication failures. The fix involves ensuring Intervat can access the most current JWK keys, restoring seamless communication with Intervat.
Original PR description
When we open a connection in intervat, we initialize a JWK on IAP side,
then we use the private key linked with this JWK to sign our requests.
The problem is on IAP, we have a cron who archive JWK older than a week.
As the archived JWK are hidden in our JWKS endpoint, Intervat is no
longer capable of verifying our signatures, leading to this error:
`{"error_description":"JWT is not valid" "error":"invalid_client"}`.
To fix this, we might need to call IAP first to unarchive the JWK first.
no-task
Forward-Port-Of: odoo/enterprise#112719This update addresses an issue where incorrect DTE (Digital Tax Document) XML files were causing the system to generate invoices even when they were invalid. The fix reintroduces a check to discard these files, preventing the creation of unnecessary invoices and ensuring data accuracy. This improves the reliability of the purchase order process.
Original PR description
A supplier DTE xml should be discard when being fetched by a DTE incoming server if it has the wrong document type, meaning no account move should be created from it. Steps: - Have purchase journal using documents - Setup an incoming mail server, with DTE option enable, with email address X - Send an email to X with a supplier DTE xml of type 52 (TipoDTE element) - Fetch mails from the incoming server -> a bill has been generated and filled, it shouldn't Cause: The check on document type has been removed with the refactor 42744fcecdbd36ea0101070c68299227a9f204a6 Fix: Reintroduce the check in `_process_incoming_supplier_document` before creating any record opw-5978959 Forward-Port-Of: odoo/enterprise#112877