Thursday, June 5, 2025
9 changes · 17.0
Enhancements to existing features
Romanian chart of accounts and tax report wording has been corrected to remove typos, improve diacritics, and use more precise official accounting terminology. This helps Romanian users read financial accounts and reports more clearly and supports better alignment with local accounting standards.
Original PR description
Description of the issue/feature this PR addresses: Some Romanian translations in the chart of accounts contained typos or imprecise terminology. These inaccuracies could lead to confusion for users relying on the Romanian localization. Current behavior before PR: Several account descriptions in Romanian included spelling errors or used vague or non-standard accounting terms. Desired behavior after PR is merged: Account descriptions in Romanian are now corrected, clearer, and better aligned with official terminology, improving usability and compliance with Romanian accounting norms. The updated translations are based on the official ANAF reference: [SAF-T RO Schema Definition Codes v4.1.6](https://static.anaf.ro/static/10/Anaf/Informatii_R/SAF_T_Ro_SchemaDefinitionCodes_v4_1_6_final_1712021.xlsx) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
The early payment discount message now displays with the correct layout and styling in the payment registration flow. This makes the discount information clearer for users and avoids confusion when processing payments.
Original PR description
Before this commit: ---- -The early payment discount message was not displayed correctly in versions 17.0 to 17.4. UI before fix: ---  After this commit: ---- -The banner UI has been fixed by applying the correct CSS classes, ensuring proper alignment and consistent styling. UI after fix: --- 
Miscellaneous changes
Steps to reproduce ================== - Open the JS unit test page - Enable the "Mid-tier mobile" option in the devtools in order to have a 4X CPU slowdown - Run the test "url should not use the record last updated date when the field is related" => It fails Cause of the issue ================== We check that a timestamp generated after a patchDate is at most 100ms after. When we have a high CPU usage or a slow CPU, it can happen that the value is more than 100ms after. Soluti
Original PR description
Steps to reproduce ================== - Open the JS unit test page - Enable the "Mid-tier mobile" option in the devtools in order to have a 4X CPU slowdown - Run the test "url should not use the record last updated date when the field is related" => It fails Cause of the issue ================== We check that a timestamp generated after a patchDate is at most 100ms after. When we have a high CPU usage or a slow CPU, it can happen that the value is more than 100ms after. Solution ======== The test simply needs to check that the date is either the `2017-02-06` or the `2017-02-09`. We can use the luxon function `a.hasSame(b, "days")` runbot-115469 Forward-Port-Of: odoo/odoo#212515
Uploading supplier bill XML files that use alphabetic electronic address scheme codes now works correctly. This prevents import errors for companies exchanging invoices through Peppol or similar e-invoicing formats.
Original PR description
Before this commit, creating bills through uploading XMLs with alphabetic codes in SchemeID was causing an error. This happened because these codes were not allowed in partner peppol_eas selection field. This commit adds these alphabetic codes as indicated in this reference sheet: https://ec.europa.eu/digital-building-blocks/sites/download/attachments/467108974/Electronic%20Address%20Scheme%20Code%20list%20-%20version%205%20-%20published.xlsx?version=1&modificationDate=1639417211464&api=v2 task-4823915 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents Mexican electronic invoices with external trade details from failing when the UMT quantity is set to zero. Businesses can now send these invoices without encountering an unexpected system error, improving reliability for edge-case invoice data.
Original PR description
With an MX Company setup: - Have a product with MX info correctly setup for external trade - Create an invoice - Set the external trade to definitive - Add the product on the invoice line and set "Qty UMT" to 0 Try to send and you will get a traceback opw-4807271
Scenario: - add an URL rewrite (308) of a route with only GET method (eg. test_website route /get rewritten to /get_new) - add a link in any website page to the original route (eg. /get) - open that page as public or user without website editing right Issue: an error 500 is shown instead of the page Cause: since the introduction of URL rewritting in be8fc2296b3822baffe0bc68cb4b7efdfe53fa91 the url_for method only worked for rewrite of route that had a POST method. In a GET method t
Original PR description
Scenario: - add an URL rewrite (308) of a route with only GET method (eg. test_website route /get rewritten to /get_new) - add a link in any website page to the original route (eg. /get) - open that page as public or user without website editing right Issue: an error 500 is shown instead of the page Cause: since the introduction of URL rewritting in be8fc2296b3822baffe0bc68cb4b7efdfe53fa91 the url_for method only worked for rewrite of route that had a POST method. In a GET method there was no try/except to handle a rewrite. Fix: handle GET method rewrite as it's done for POST method. Note: the added test without the fix fails with a 500 status code instead of the 200 expected. opw-4817473 Forward-Port-Of: odoo/odoo#212969
Description of the issue/feature this PR addresses: Issue: if only one line is edited/added and it's account is not of type off-balance, the check will fail to raise the warning Steps to reproduce the error: 1. Create entry 2. Account move line 1 with account off balance 3. Account move line 2 with account off balance 4. Save move 5. Edit line 2, change the account to an asset type account. 6. Save move. The system does not give a warning. Current behavior before PR: Desired beha
Original PR description
Description of the issue/feature this PR addresses: Issue: if only one line is edited/added and it's account is not of type off-balance, the check will fail to raise the warning Steps to reproduce the error: 1. Create entry 2. Account move line 1 with account off balance 3. Account move line 2 with account off balance 4. Save move 5. Edit line 2, change the account to an asset type account. 6. Save move. The system does not give a warning. Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#211811
The XML already reports **PesoBrutoVehicular** in metric tonnes, as required by the Carta Porte complement. However, the PDF layout labelled the value as **kg**. * Updated QWeb template to display the unit `t`. Legal basis ----------- * Complemento Carta Porte 3.1 – Instructivo de llenado: “Peso Bruto Vehicular… atributo requerido para indicar **en toneladas** el peso bruto vehicular permitido… de acuerdo con la NOM-SCT-012-2017”. :contentReference[oaicite:0]{index=0} Forward-Port-Of:
Original PR description
The XML already reports **PesoBrutoVehicular** in metric tonnes, as required by the Carta Porte complement.
However, the PDF layout labelled the value as **kg**.
* Updated QWeb template to display the unit `t`.
Legal basis
-----------
* Complemento Carta Porte 3.1 – Instructivo de llenado: “Peso Bruto Vehicular… atributo requerido para indicar **en toneladas** el peso bruto vehicular permitido… de acuerdo con la NOM-SCT-012-2017”. :contentReference[oaicite:0]{index=0}
Forward-Port-Of: odoo/enterprise#85798This commit 1ba25b9d5d4e2d68084aa3705ba897823cc936f9 introduced a bug. It was not possible anymore to duplicate a product. Now, we make sure that we're able to log properly the product name when we create or duplicate the product. Forward-Port-Of: odoo/enterprise#83826
Original PR description
This commit 1ba25b9d5d4e2d68084aa3705ba897823cc936f9 introduced a bug. It was not possible anymore to duplicate a product. Now, we make sure that we're able to log properly the product name when we create or duplicate the product. Forward-Port-Of: odoo/enterprise#83826