Monday, October 21, 2024
11 changes · 17.0
New functionality added to Odoo
Added new versions of Balance Sheet and Profit & Loss reports for Dutch companies that use account tags instead of account codes. This provides an alternative reporting method that better aligns with how Dutch businesses typically organize their chart of accounts, making financial reporting more flexible and user-friendly.
Original PR description
In the Netherlands localization, the Balance Sheet and Profit&Loss reports are only currently built on account codes. We want to add another version of the accounting reports that uses account tags. Community PR: odoo/odoo#157362 Task link: https://www.odoo.com/web#model=project.task&id=3794536 task-3794536
Enhancements to existing features
Odoo now supports Chinese Yuan (CNY) currency exchange rates from the Banxico provider. Previously, only USD, EUR, JPY, and GBP were available. This expansion allows businesses operating in or with China to access live currency conversion rates through the same Banxico data source.
Original PR description
Currently, Odoo supports several currencies (USD, EUR, JPY, GBP) for Banxico data parsing, but CNY (Chinese Yuan) is missing. This commit adds support for CNY in the list of currencies retrieved from Banxico’s API (through iap proxy). related pr: https://github.com/odoo/iap-apps/pull/912 task-4205613
Resolved issues and error corrections
This update corrects a problem with the Spanish VAT reporting model (Modelo 349) that was preventing accurate report generation. The changes include updated wording, a new calculation engine for rectifications, and fixes for data errors like negative amounts and incorrect discount calculations. This ensures accurate VAT reporting for Spanish businesses.
Original PR description
The model 349 wasn't working as expected, here are the points that have been changed: - Some keys were missing, in particular the keys R, D, and C. - Changed some wording of the report, such as replacing 'refunds' with 'rectifications'. - The biggest change was changing the way the lines are computed in the report. Before this commit, we used only the domain engine, but now we need to use a custom engine to handle the rectifications part. - Fixed some other bugs, like negative amounts which are not supposed to appear as the report only deals with positive values, and also ensured the discounts on the move lines are computed correctly. task-3992046 Forward-Port-Of: odoo/enterprise#65074
This update corrects a variable scope problem in the Peru electronic invoicing stock module that was causing incorrect values to be used in certain operations. The fix ensures that the correct data is referenced when processing stock movements for Peru's electronic document system, improving the accuracy of EDI compliance.
Original PR description
Forward-Port-Of: odoo/enterprise#72307
This update fixes how GST tax rates are calculated in Indian tax reports by properly tracking different tax types (IGST, CGST, SGST) separately before combining them. This ensures that businesses filing GST returns get accurate tax rate calculations, especially when multiple tax types apply to the same transaction.
Original PR description
In this PR: - Added a `rate_by_tax_tag` dictionary to store tax rates by tax type (IGST, CGST, SGST) at the line level. - Adjusted the logic to populate `gst_tax_rate` by summing the values from `rate_by_tax_tag`, ensuring accurate tax rate calculations when multiple tax types are involved. - This change improves handling of scenarios with different tax types and ensures consistent and accurate GST reporting.
Fixed a bug in the manufacturing shop floor where the Quality Checks button would remain visible and cause errors even after quality checks were already completed. The system now properly updates its internal record reference when production data changes, ensuring the interface stays in sync with the actual production status.
Original PR description
## Steps to reproduce: 1. Create a quality control point for the operation type Manufacturing 2. Create a manufacturing order and plan it 3. Go to the Shop floor 4. Register the production & do the quality checks 5. The Quality Checks button is still there; clicking again displays a traceback because the quality checks are already done. ## Before this commit: Upon reloading the production, the new data is not propagated to `this.record`. ## After this commit: Change `this.record` when props are updated so it always contains the correct reference to the record. opw-4176393
This fix corrects a bug in the Brazilian electronic invoice system where messages were being posted to the wrong invoice. The issue was detected by an automated code quality check and has been resolved to ensure messages are properly associated with their correct invoices.
Original PR description
Spotted by runbot in master by the `self-in-iter` semgrep check.
Fixed an issue where authorized users couldn't duplicate document templates due to insufficient access rights. The system now properly handles permissions when creating a copy of a template, allowing users with the appropriate authorization to successfully duplicate templates without encountering errors.
Original PR description
To reproduce: ============= - log as admin and create a template on sign - give a user with **User : Own templates** authorization to the template - log as the user and try to use layout (from 3 dots in kanban view) -> access error Problem: ======== when duplicating the template we copy the original template, as the user does not have enough rights it leads to an access error Solution: ========= perform the copy as `sudo`, as the template won't be visible for the user if he is not authorized to see it. opw-4166973 Forward-Port-Of: odoo/enterprise#70496
This update corrects an incorrect reference in the US payroll accounting module. The system was looking for the wrong chart template name and has been fixed to use the correct generic chart of accounts template. This ensures proper accounting setup for US payroll operations.
Original PR description
Currently we search for the 'us' chart template but we should search for the 'generic_coa' instead. This commit corrects it. task-None
This update fixes an issue where demo project stages were being removed when they were already in use by other projects. By removing default stages before assigning new ones, the system now prevents conflicts between demo data from different modules, ensuring a smoother setup experience.
Original PR description
Remove the default stages before assigning new stages to the demo project. This update prevents the removal of stages that are being used in other projects, thereby avoiding conflicts with demo data from other modules.
This fix corrects a variable scope problem in the Peru EDI stock picking functionality. The issue was causing incorrect values to be used in the stock module's EDI processing, which could affect the accuracy of electronic document generation for inventory movements in Peru.