Daily updates from Odoo
Saturday, February 14, 2026
3 changes · saas-18.3
Enhancements to existing features
This update improves the generation of XML files for HR tax reporting (l10n_hr_edi) by streamlining processes and adding more robust testing. Specifically, the system now handles multiple tax totals and categories correctly, and includes new tests to ensure accurate invoice exemption processing and fiscalization queries are limited to own documents.
Original PR description
- Improving the ubl_hr method chain to include less overrides in favor of extensions - Adding proper handling of multiple tax total and tax category nodes for hrextac - Refining docstrings and comments for ubl_hr - Adding a test with multiple tax types - Adding a test for account_edi_ubl_cii_tax_extension integration - Adjusting MER methods to correspond to API changes: fiscalization queries are now only available for own documents task-none --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#247339
Resolved issues and error corrections
This update addresses an issue where invoices imported through the account_edi_ubl_cii module were incorrectly processing zero values for certain line amounts. The change ensures that these zero values are simply ignored during import, preventing potential errors and ensuring data accuracy. This improves the reliability of invoice processing.
Original PR description
Zero LineExtensionAmount have no purpose after import so they can simply be ignored. taks-5881008 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#248732 Forward-Port-Of: odoo/odoo#245862
This update significantly improves the performance of the MPS report by reducing memory usage when processing large production schedules. The changes optimize data retrieval and minimize unnecessary data fetching, resulting in faster report generation and preventing potential errors. This enhancement ensures a smoother experience for users generating these reports.
Original PR description
Problem: When running the MPS report on a large number of production schedules, if the associated number of stock moves is high, the _get_moves_and_date method can cause a memory error. Solution: We…
Problem:
When running the MPS report on a large number of production schedules, if the associated number of stock moves is high, the _get_moves_and_date method can cause a memory error.
Solution:
We will fetch only the necessary fields to reduce queries and memory usage and set prefetch_fields=False to further reduce memory usage.
Benchmarks:
Run locally on a dupe of customer's db.
Time/queries measured by requests to /get_mps_view_state Memory measured using memray on method get_production_schedule_view_state()
<table>
<tr>
<th rowspan="2"># of Production Schedules</th>
<th colspan="3">Before</th>
<th colspan="3">After</th>
</tr>
<tr>
<th>Time</th>
<th># of Queries</th>
<th>Memory usage</th>
<th>Time</th>
<th># of Queries</th>
<th>Memory usage</th>
</tr>
<tr>
<td>20</td>
<td>22.846s</td>
<td>1,379</td>
<td>882.0MB</td>
<td>8.046s</td>
<td>1,180</td>
<td>103.4MB</td>
</tr>
<tr>
<td>300</td>
<td>41.098s</td>
<td>6,297</td>
<td>1.0GB</td>
<td>43.694s</td>
<td>5,732</td>
<td>363.5MB</td>
</tr>
<tr>
<td>1000</td>
<td>N/A (MemoryError)</td>
<td>N/A (MemoryError)</td>
<td>>2GB</td>
<td>88.416s</td>
<td>22,629</td>
<td>1.1GB</td>
</tr>
</table>
Average memory usage reduction: 75%
opw-5225472
Forward-Port-Of: odoo/enterprise#106392