Daily updates from Odoo
Navigate
Branch
Saturday, May 2, 2026
20 changes
5 changes
Resolved issues and error corrections
This update fixes an issue where order reports, particularly those using the 'From the very start' period, displayed unordered string-based external values. The change ensures that these values are now correctly sorted by date, improving the accuracy and reliability of financial reporting.
Original PR description
Ensure string-type external values are correctly sorted by date when using the "most_recent" formula. This resolves an issue where values appeared unordered, especially for expressions using the "From the very start" period. task-5951888 Forward-Port-Of: odoo/enterprise#115275 Forward-Port-Of: odoo/enterprise#113837
This update resolves a technical issue related to how the CDR (Electronic Delivery Guide) is processed in the l10n_pe_edi_stock module. The fix corrects errors caused by changes in how binary data is handled, ensuring proper PDF generation for delivery slips and preventing errors when attaching CDRs to delivery guides. This ensures accurate e-invoicing functionality for Peru.
Original PR description
Two issues both stemming from the Binary field changes in odoo/enterprise#104714: 1/ `_l10n_pe_edi_unzip_edi_document` returns the CDR as bytes (from `zipfile.read()`), so calling `.encode()` on it raises `AttributeError: 'bytes' object has no attribute 'encode'` when attaching the CDR to a sent delivery guide. 2/ `attachment.raw` no longer returns bytes but a `BinaryValue`, so `etree.fromstring(attachment.raw)` in `_l10n_pe_edi_get_qr` raises `ValueError: can only parse strings` when rendering the delivery slip PDF for a sent picking. Use `attachment.raw.content` to get the bytes. The existing test missed both because it patched `_l10n_pe_edi_sign` to return a `str` and never rendered the report. Patch with `bytes` to match what the real method returns and render the delivery slip to exercise `_l10n_pe_edi_get_qr` end-to-end. task-6107987 (found these bugs while working on)
This update resolves a crash issue during FEC imports for French association companies in Guadeloupe and Martinique. The fix prevents the import process from incorrectly attempting to link asset models, which were previously causing errors. This ensures smoother and more reliable FEC imports for our French users.
Original PR description
Description of the issue: Importing an FEC on saas-19.1 can crash for French association companies in Guadeloupe or Martinique. During the import, account data is completed from the fr_comp account…
Description of the issue: Importing an FEC on saas-19.1 can crash for French association companies in Guadeloupe or Martinique. During the import, account data is completed from the fr_comp account templates. Since 19.1, those templates may include asset_model_ids, which makes the import try to resolve asset XML IDs that do not exist for that company setup. Steps to reproduce: 1. Create a new company with Guadeloupe or Martinique for country. 2. Set the French associations chart of accounts on it. 3. Go to Accounting -> Configuration -> Chart of Accounts. 4. Import the FEC file linked on the ticket. 5. Import fails with traceback. Desired behavior after fix: FEC import should keep the existing template completion behavior, but it should not copy asset_model_ids onto imported accounts. Importing an FEC for French association companies in Guadeloupe or Martinique should therefore no longer crash because of unrelated asset model references. Ticket [link](https://www.odoo.com/odoo/project.task/6053048) opw-6053048 Forward-Port-Of: odoo/enterprise#114799
This update fixes a minor usability issue in the bank reconciliation creation process. Previously, an error would open a form dialog unexpectedly. Now, errors are displayed directly, providing a clearer and more intuitive user experience for creating bank reconciliation records.
Original PR description
Before this commit, when there is an error in the bank rec widget quick create. We open the form dialog which is kind a weird, we would rather expect to have the error displayed. This commit will override the showFormDialogInError to close the quick create and throw the error. no task id Forward-Port-Of: odoo/enterprise#115432
This update resolves a minor configuration issue within Odoo's settings file (odoo.conf). Specifically, the way the Egyptian token is accessed has been corrected to use 'options' instead of 'default'. This ensures proper functionality and avoids potential retrieval problems.
Original PR description
This PR fixes the section used to retrieve the egyptian token in odoo.conf file for it to be "options" instead of "default" Related PR: https://github.com/odoo/odoo/pull/255121 Forward-Port-Of: odoo/odoo#262078 Forward-Port-Of: odoo/odoo#262006
4 changes
Resolved issues and error corrections
This update fixes an issue where date-based reports, particularly those using the 'From the very start' period, displayed unordered results. The change ensures string-type external values are now correctly sorted by date, improving the accuracy and reliability of financial reporting.
Original PR description
Ensure string-type external values are correctly sorted by date when using the "most_recent" formula. This resolves an issue where values appeared unordered, especially for expressions using the "From the very start" period. task-5951888 Forward-Port-Of: odoo/enterprise#115275 Forward-Port-Of: odoo/enterprise#113837
This update resolves a crash issue during FEC imports for French association companies in Guadeloupe and Martinique. The fix prevents the import process from incorrectly attempting to link asset models, which were causing errors. This ensures smoother and more reliable FEC imports for our French users.
Original PR description
Description of the issue: Importing an FEC on saas-19.1 can crash for French association companies in Guadeloupe or Martinique. During the import, account data is completed from the fr_comp account…
Description of the issue: Importing an FEC on saas-19.1 can crash for French association companies in Guadeloupe or Martinique. During the import, account data is completed from the fr_comp account templates. Since 19.1, those templates may include asset_model_ids, which makes the import try to resolve asset XML IDs that do not exist for that company setup. Steps to reproduce: 1. Create a new company with Guadeloupe or Martinique for country. 2. Set the French associations chart of accounts on it. 3. Go to Accounting -> Configuration -> Chart of Accounts. 4. Import the FEC file linked on the ticket. 5. Import fails with traceback. Desired behavior after fix: FEC import should keep the existing template completion behavior, but it should not copy asset_model_ids onto imported accounts. Importing an FEC for French association companies in Guadeloupe or Martinique should therefore no longer crash because of unrelated asset model references. Ticket [link](https://www.odoo.com/odoo/project.task/6053048) opw-6053048 Forward-Port-Of: odoo/enterprise#114799
This update enhances the user experience when creating bank reconciliation entries. Previously, an error would open a form dialog unexpectedly. Now, errors are displayed directly, providing clearer feedback and simplifying the process for users.
Original PR description
Before this commit, when there is an error in the bank rec widget quick create. We open the form dialog which is kind a weird, we would rather expect to have the error displayed. This commit will override the showFormDialogInError to close the quick create and throw the error. no task id Forward-Port-Of: odoo/enterprise#115432
This update resolves an issue related to how a specific token is configured within Odoo's settings file (odoo.conf). The change ensures the correct setting is used, improving the stability and functionality of the IoT drivers. This resolves a technical detail that was impacting the system.
Original PR description
This PR fixes the section used to retrieve the egyptian token in odoo.conf file for it to be "options" instead of "default" Related PR: https://github.com/odoo/odoo/pull/255121 Forward-Port-Of: odoo/odoo#262078 Forward-Port-Of: odoo/odoo#262006
2 changes
Resolved issues and error corrections
This update fixes an issue where financial reports, particularly those using the 'From the very start' period, displayed unordered string external values. The change ensures that these values are now correctly sorted by date, improving the accuracy and reliability of financial reporting.
Original PR description
Ensure string-type external values are correctly sorted by date when using the "most_recent" formula. This resolves an issue where values appeared unordered, especially for expressions using the "From the very start" period. task-5951888 Forward-Port-Of: odoo/enterprise#115275 Forward-Port-Of: odoo/enterprise#113837
This update fixes a minor usability issue in the quick creation of bank reconciliation entries. Previously, an error would open a dialog box instead of displaying the error directly. This change ensures errors are clearly shown, improving the user experience and making it easier to correct mistakes.
Original PR description
Before this commit, when there is an error in the bank rec widget quick create. We open the form dialog which is kind a weird, we would rather expect to have the error displayed. This commit will override the showFormDialogInError to close the quick create and throw the error. no task id Forward-Port-Of: odoo/enterprise#115432
1 change
Resolved issues and error corrections
This update fixes an issue where date-based order reports (specifically using the 'most_recent' formula) were displaying unordered results. The change ensures that string-type external values are correctly sorted by date, resolving inconsistencies and improving the accuracy of financial reporting. This impacts how recent order data is presented.
Original PR description
Ensure string-type external values are correctly sorted by date when using the "most_recent" formula. This resolves an issue where values appeared unordered, especially for expressions using the "From the very start" period. task-5951888 Forward-Port-Of: odoo/enterprise#115275 Forward-Port-Of: odoo/enterprise#113837
1 change
Resolved issues and error corrections
This update fixes an issue where order reports were displaying string-based external values in an unordered fashion, particularly when using the 'From the very start' period. The change ensures that string values are now correctly sorted by date, improving the accuracy and reliability of order report data.
Original PR description
Ensure string-type external values are correctly sorted by date when using the "most_recent" formula. This resolves an issue where values appeared unordered, especially for expressions using the "From the very start" period. task-5951888 Forward-Port-Of: odoo/enterprise#115275 Forward-Port-Of: odoo/enterprise#113837
5 changes
Resolved issues and error corrections
This update resolves a technical issue causing TypeErrors during testing of Odoo's tax processing (l10n_do_edi) module. The fix ensures error messages are correctly formatted, preventing test failures and improving the stability of tax calculations.
Original PR description
Problem: A TypeError traceback occurs with the test cases because the error was not formatted properly from l10n_do_edi_blocking_errors when _format_error_text is called. Solution: Map the error message properly in l10n_do_edi_blocking_errors. Related PR: https://github.com/odoo/enterprise/pull/112814 runbot-build-error-242502 Forward-Port-Of: odoo/enterprise#114392
This update fixes an issue where order reports, particularly those using the 'From the very start' period, displayed string-based external values in an unordered fashion. The change ensures that these values are now correctly sorted by date, improving the accuracy and reliability of financial reporting.
Original PR description
Ensure string-type external values are correctly sorted by date when using the "most_recent" formula. This resolves an issue where values appeared unordered, especially for expressions using the "From the very start" period. task-5951888 Forward-Port-Of: odoo/enterprise#115275 Forward-Port-Of: odoo/enterprise#113837
This update resolves a technical problem related to how the CDR (Electronic Delivery Document) is processed within the Odoo Enterprise system. Specifically, changes in how binary data is handled caused errors during PDF generation for delivery slips. This fix ensures accurate processing of CDR data, preventing disruptions to delivery tracking and reporting.
Original PR description
Two issues both stemming from the Binary field changes in odoo/enterprise#104714: 1/ `_l10n_pe_edi_unzip_edi_document` returns the CDR as bytes (from `zipfile.read()`), so calling `.encode()` on it raises `AttributeError: 'bytes' object has no attribute 'encode'` when attaching the CDR to a sent delivery guide. 2/ `attachment.raw` no longer returns bytes but a `BinaryValue`, so `etree.fromstring(attachment.raw)` in `_l10n_pe_edi_get_qr` raises `ValueError: can only parse strings` when rendering the delivery slip PDF for a sent picking. Use `attachment.raw.content` to get the bytes. The existing test missed both because it patched `_l10n_pe_edi_sign` to return a `str` and never rendered the report. Patch with `bytes` to match what the real method returns and render the delivery slip to exercise `_l10n_pe_edi_get_qr` end-to-end. task-6107987 (found these bugs while working on) Forward-Port-Of: odoo/enterprise#115958
This update resolves an issue causing FEC imports to crash for French association companies in Guadeloupe and Martinique. The fix prevents the import process from incorrectly attempting to link asset models, which were unexpectedly included in the account templates. This ensures smoother and more reliable FEC imports for these specific company setups.
Original PR description
Description of the issue: Importing an FEC on saas-19.1 can crash for French association companies in Guadeloupe or Martinique. During the import, account data is completed from the fr_comp account…
Description of the issue: Importing an FEC on saas-19.1 can crash for French association companies in Guadeloupe or Martinique. During the import, account data is completed from the fr_comp account templates. Since 19.1, those templates may include asset_model_ids, which makes the import try to resolve asset XML IDs that do not exist for that company setup. Steps to reproduce: 1. Create a new company with Guadeloupe or Martinique for country. 2. Set the French associations chart of accounts on it. 3. Go to Accounting -> Configuration -> Chart of Accounts. 4. Import the FEC file linked on the ticket. 5. Import fails with traceback. Desired behavior after fix: FEC import should keep the existing template completion behavior, but it should not copy asset_model_ids onto imported accounts. Importing an FEC for French association companies in Guadeloupe or Martinique should therefore no longer crash because of unrelated asset model references. Ticket [link](https://www.odoo.com/odoo/project.task/6053048) opw-6053048 Forward-Port-Of: odoo/enterprise#114799
This update fixes a previous issue where an error in the bank reconciliation quick create form would unexpectedly open a dialog box. Now, errors are displayed directly, providing a clearer and more intuitive user experience. This change improves usability and ensures users immediately see and address any problems during bank reconciliation setup.
Original PR description
Before this commit, when there is an error in the bank rec widget quick create. We open the form dialog which is kind a weird, we would rather expect to have the error displayed. This commit will override the showFormDialogInError to close the quick create and throw the error. no task id Forward-Port-Of: odoo/enterprise#115432
1 change
Resolved issues and error corrections
This update fixes an issue where financial reports, particularly those using the 'From the very start' period, displayed unordered string external values. The change ensures that string-type dates are now correctly sorted, improving the accuracy and reliability of financial reporting data.
Original PR description
Ensure string-type external values are correctly sorted by date when using the "most_recent" formula. This resolves an issue where values appeared unordered, especially for expressions using the "From the very start" period. task-5951888 Forward-Port-Of: odoo/enterprise#115275 Forward-Port-Of: odoo/enterprise#113837
1 change
Resolved issues and error corrections
This update clarifies the origin of subcontracted manufacturing orders (MOs). Previously, users couldn't easily see where the MO originated from, making it difficult to track the process. Now, the picking number is added to the MO's origin, providing better visibility and traceability for subcontracted production.
Original PR description
* Currently when viewing subcontract MO (maybe from Valuation report) we do not where it comes from, not source origin, very hard for user to visualize * After this commit: add picking number to origin of subcontract MO Backport of https://github.com/odoo/odoo/pull/209695 Description of the issue/feature this PR addresses: 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