Daily updates from Odoo
Saturday, February 8, 2025
7 changes · master
Miscellaneous changes
**Steps to reproduce:** Use a Colombian company. Configure DIAN / Carvajal (company, product, and supplier) as per documentation. Change the language to Spanish (LATAM). Create a new Purchase Order using the supplier and the product: - Receive the product. - Create the Vendor Bill: - Change the Journal to the DIAN Support Documents journal and set the date. - Using the actions, print the invoice (even without payment) and look at the document title. [](https://github.com/user-attachments/files/18359586/SEDS_2025_01_0014.pdf) - Create a Credit Note: - Using the actions, print the credit note (even without payment) and look at the document title. [](https://github.com/user-attachments/files/18359584/RSEDS_2025_01_0009.pdf) --- **Issue:** DIAN vendor bills and vendor credit notes display `Factura de proveedor` and `Nota de crédito de proveedor`. --- **Expected:** DIAN vendor bills and vendor credit notes should display `Documento Soporte` and `Nota de Ajuste del Documento Soporte`. --- **Cause:** Vendor bills and credit notes are not managed by Colombian's EDI nor DIAN modules but only by the Account module. --- **Fix:** Add DIAN-specific `Vendor Bill` and `Vendor Credit Note` translations. Manage the title replacement in the generated file if the PDF generation is done by the DIAN module. [](https://github.com/user-attachments/files/18359493/SEDS_2025_01_0013.pdf) [](https://github.com/user-attachments/files/18359499/RSEDS_2025_01_0008.pdf) --- **Task References:** opw-4423439 opw-4433918 Forward-Port-Of: odoo/enterprise#78819 Forward-Port-Of: odoo/enterprise#76793
Before this commit, In kanban view when selecting multiple documents while holding shift as modifier, it could happen that folders were selected too. This was due to the logic which was using document ids as the range value when looping on `root.records` but with the new UI where the folders are now displayed on top of the documents it was buggy. In list view, we would like to keep the same behavior as in other list views. This commit fixes those issues. Task-4532046 Forward-Port-Of: o
Original PR description
Before this commit, In kanban view when selecting multiple documents while holding shift as modifier, it could happen that folders were selected too. This was due to the logic which was using document ids as the range value when looping on `root.records` but with the new UI where the folders are now displayed on top of the documents it was buggy. In list view, we would like to keep the same behavior as in other list views. This commit fixes those issues. Task-4532046 Forward-Port-Of: odoo/enterprise#78196
Forward-Port-Of: odoo/enterprise#78842
Original PR description
Forward-Port-Of: odoo/enterprise#78842
In 18.0, we dropped the support for the round per line rounding method in Mexico. However, we didn't think about the following scenario: - a user creates an invoice in 17.0 in round-per-line mode, and sends it to the Mexican government without problem - they then upgrade to 18.0 - a while later, they receive payment for the invoice. They then try to send the payment CFDI to the Mexican government. The payment CFDI is a complicated beast because it needs to retrieve values from the i
Original PR description
In 18.0, we dropped the support for the round per line rounding method in Mexico. However, we didn't think about the following scenario: - a user creates an invoice in 17.0 in round-per-line mode,…
In 18.0, we dropped the support for the round per line rounding method in Mexico. However, we didn't think about the following scenario: - a user creates an invoice in 17.0 in round-per-line mode, and sends it to the Mexican government without problem - they then upgrade to 18.0 - a while later, they receive payment for the invoice. They then try to send the payment CFDI to the Mexican government. The payment CFDI is a complicated beast because it needs to retrieve values from the invoice the payment was reconciled with. Since the amounts in the invoice are slightly different from what they should be in round globally, the payment CFDI gets incorrectly generated and gets rejected by the Mexican government. So we need a temporary fix that allows the values of the payment CFDI to be adjusted according to the values of the invoice, which works even if the invoice used round per line. This fix is inspired by the existing solution in version 17: https://github.com/odoo/enterprise/pull/68319 and ensures that the "importe" amount is properly calculated. opw-4537931 opw-4536649 opw-4528785 opw-4490806 Forward-Port-Of: odoo/enterprise#78674
Version - 18.0 Problem - The translation button in the studio reports is hidden/ not accessible to the customer Steps to reproduce- Open Sales app > Go to the Studio view > Select Reports from the menu > Open any report among the listed ones On the left hand side - in the studio editor select "Edit Source" On the Edit source file - In the initial version there used to be an EN (Translation button) for them to translate the display field names opw-4417402 Forward-Port-Of: odoo/enterprise
Original PR description
Version - 18.0 Problem - The translation button in the studio reports is hidden/ not accessible to the customer Steps to reproduce- Open Sales app > Go to the Studio view > Select Reports from the menu > Open any report among the listed ones On the left hand side - in the studio editor select "Edit Source" On the Edit source file - In the initial version there used to be an EN (Translation button) for them to translate the display field names opw-4417402 Forward-Port-Of: odoo/enterprise#78462
HTML content is often saved as XML (i.e. through templates) and saved as such in the database. This introduces issues when elements are written under their `self-closing` format (i.e. `<a/>` or `<br/>`) as browsers will incorrectly parse these values as HTML by adding a closing tag at an arbitrary position which may modify the initial nodes configuration. This can be prevented by post-processing untrusted content before the html parsing. Check this commit community counterparts, which place t
Original PR description
HTML content is often saved as XML (i.e. through templates) and saved as such in the database. This introduces issues when elements are written under their `self-closing` format (i.e. `<a/>` or `<br/>`) as browsers will incorrectly parse these values as HTML by adding a closing tag at an arbitrary position which may modify the initial nodes configuration. This can be prevented by post-processing untrusted content before the html parsing. Check this commit community counterparts, which place the conversion responsibility in the `html_viewer` instead of the `html_upgrade_manager`. task-4547973 Forward-Port-Of: odoo/enterprise#78532
The issue occurs because the query does not apply an offset or limit, causing the same lines to be loaded repeatedly. This results in duplicate keys on the client side. To fix this, we add a query tail and mimic the ordering of account_move_line, ensuring consistency when loading additional lines. This fix is related to an earlier patch in older versions, but due to the refactoring of the Intrastat report, it had to be implemented differently. Old Fix: https://github.com/odoo/enterprise
Original PR description
The issue occurs because the query does not apply an offset or limit, causing the same lines to be loaded repeatedly. This results in duplicate keys on the client side. To fix this, we add a query tail and mimic the ordering of account_move_line, ensuring consistency when loading additional lines. This fix is related to an earlier patch in older versions, but due to the refactoring of the Intrastat report, it had to be implemented differently. Old Fix: https://github.com/odoo/enterprise/pull/76543 Forward-Port-Of: odoo/enterprise#78743 Forward-Port-Of: odoo/enterprise#78628