Saturday, April 4, 2026
5 changes · 19.0
Resolved issues and error corrections
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 other documents like ‘e-Remito’ and ‘e-Resguardos’ are handled, 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 fixes an issue on mobile devices where the buttons within the transfer chatter view were too small, causing text to overflow and making the interface difficult to use. The change ensures that buttons are properly sized and display all text clearly, improving the user experience on mobile. This resolves a reported usability problem.
Original PR description
Partial backport of d16480179ed73f25e0465e42c6fdef64e4fdc502 Steps to reproduce ================== - Navigate to Barcode, click on any transfer - Click on the name of the transfer in the header to open the form view - Scroll down to the chatter, the buttons are too small to contain the text, and much of the text flows over to other UI elements Cause of the issue ================== The barcode style override every buttons including the ones inside the chatter opw-6082959 Forward-Port-Of: odoo/enterprise#112581
This update fixes an issue where incorrect DTE (Digital Tax Document) XML files received by the system were automatically generating invoices. The fix reintroduces a check to discard these invalid DTEs, preventing the creation of unnecessary invoices and ensuring data accuracy. This improves the reliability of the purchase journal.
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
This update reorganizes test code to ensure tests are located in the same module where the test models they use are defined. A test was moved from the base module to the test_testing_utilities module where the res.config.test model is actually defined. This improves code organization and maintainability without affecting any user-facing functionality.
Original PR description
Move the test to test_testing_utilities where the model res.config.test is defined. Move test introduced in odoo/odoo#257033. runbot-242309 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#257514
Miscellaneous changes
This pull request contains internal testing updates for the account_online_payment module within Odoo Enterprise. These tests ensure the payment processing functionality continues to operate correctly and reliably. The changes are focused on improving the testing framework, not a customer-facing feature.
Original PR description
No task ID