Daily updates from Odoo
Thursday, December 5, 2024
9 changes · 17.0
Enhancements to existing features
This update significantly improves the accuracy of Estonia's VAT tax reports (KMD and KMD INF) by correcting rounding errors and enhancing reporting capabilities. It includes a new module to handle rounding differences between Odoo and the Estonian tax authority, ensuring compliance with updated reporting guidelines.
Original PR description
The tax report (KMD report) and annex to the tax report (KMD INF report) for Estonia needed to be reworked to correct errors and fix rounding issues. With this commit, the tax report: 1. Adds the…
The tax report (KMD report) and annex to the tax report (KMD INF report) for Estonia needed to be reworked to correct errors and fix rounding issues. With this commit, the tax report: 1. Adds the balance_from_tags to allow auditing the report lines, since only aggregation was used before. 2. Fixes rounding issues by using the integer_rounding feature and adding rounding differences to the VAT closing entry. This commit also rewrites the KMD INF report. It creates one report composed of two sections with different columns, using the custom engine to construct both parts. Part A contains information on invoices issued, grouped by move_id and id, to allow showing multiple lines per invoice when different tax rates or special tax types are in one invoice. It only includes invoices with taxable supply at 22%, 20%, 9% and 5%. It excludes invoices of partners whose Tax ID is / and foreigner partners who have a Tax ID not starting by EE. Part B contains information on invoices received, grouped by move_id. Each line showcases information about one invoice with taxable supply at 22%, 20%, 9% and 5%. It relies on a Tax ID starting with EE. The reports follow the guidelines available in https://www.emta.ee/en/business-client/taxes-and-payment/tax-returns-exchange-information/vat-return-forms-vd-and-vdp (forms valid from 01.01.2024 onwards). task-3997203
This update addresses necessary adjustments to the Danish localization package (l10n_dk) following a recent change in the community version. Specifically, tests have been updated to align with the new account type. This ensures continued accurate reporting and compliance for Danish businesses using Odoo Enterprise.
Original PR description
Following the change of account type in the community pr, some tests had to be modified. task: 4341375
Resolved issues and error corrections
This update resolves an issue where the resource name wasn't correctly updating in appointment scheduling views. The fix ensures that the selected resource is accurately displayed in the detail column, regardless of appointment type (user-based or resource-based). This improves the user experience when scheduling appointments.
Original PR description
Versions -------- - 17.0+ Steps ----- 1. Create an appointment type with availability base on resources; 2. have multiple resources to select from; 3. copy share URL; 4. open URL; 5. select a different resource. Issue ----- The resource name in the right column doesn't update to the selected resource. Cause ----- There's no logic in place to update it after selecting a different resource. Solution -------- For user-based appointments, this part isn't shown as long as there's multiple options available. Expand this logic to also work for resource-based appointments. Also modify it to now show details on date selection step unless there's only one option to select from (instead of unless pictures should be shown). With `website_appointment`, this is also the case when a separate selection screen was shown beforehand. opw-4355438
This update prevents the creation of quality checks when inventory is marked as 'Scrapped' within Odoo. Previously, a quality check was automatically generated after a 'Scrap' action, which was an unnecessary step. This change streamlines the process and ensures accurate inventory tracking.
Original PR description
Steps to reproduce the bug: - Create a storable product “P1.” - Set up a quality point: - Control Per: By operation - Operation: Receipts - Product: P1 - Create a receipt for two units of P1. - Mark the receipt as "To Do." - Click on "Quality Check" → Fail. - Click on action → Scrap: - Scrap 1 unit of P1. - Confirm. Problem: A quality check is created for the scrapped move. This should not happen. opw-4345679
This update resolves an issue where vendor bills weren't correctly associating with the correct partner (Azure Interior). The fix ensures the partner ID is populated when creating vendor bills from documents, preventing data discrepancies and improving financial reporting accuracy. This was triggered by a correction in how attachments are handled.
Original PR description
steps to reproduce: - Install documents_account - In Settings -> File centralization -> Activate "Accounting" - Then click on Journals below - Then add Jounal: Vendor Bill, Workspace: Finance - Then…
steps to reproduce: - Install documents_account - In Settings -> File centralization -> Activate "Accounting" - Then click on Journals below - Then add Jounal: Vendor Bill, Workspace: Finance - Then upload a file in the app Documents, in the workspace Finance - Select that file and update the partner to Azure Interior - Click on the action "Create Vendor Bill" The partner "Azure Interior" is not set on the created account move while it should. For fixing this adding ``partner_id`` of document if present. Now question may arise why account.move having null partner_id. because it being [set](https://github.com/odoo/enterprise/blob/64fc38a80520cfeeb81c0bb329c6b24c3e9454e1/documents_account/models/documents_workflow_rule.py#L77) after creating [attachment](https://github.com/odoo/enterprise/blob/64fc38a80520cfeeb81c0bb329c6b24c3e9454e1/documents_account/models/documents_workflow_rule.py#L76) and during create attachment ``document.partner_id`` is set to null and issue is raised. opw-4077356
This update resolves a technical error that prevented users from successfully splitting documents when scheduling activities within the Documents module. The fix ensures that document IDs are correctly included, allowing the splitting functionality to work as intended. This improves the reliability of document management workflows.
Original PR description
useEffect hook on pdf_manager generates file urls from documents ids, before this commit documents comming from activity view didn't have id key set. Reproduce --- - install document - open documents activity view, schedule an activity with a document (that is possible to split) - attempt to split the document -> Traceback opw-4163726
This update resolves an issue where deleting all stages from a helpdesk ticket kanban view resulted in a blank screen. The fix ensures that the correct data is displayed after stage deletion, improving the user experience. The problem stemmed from a validation oversight in the system.
Original PR description
Steps: - Create a new helpdesk team. - Open tickets of that team. - Delete all ticket stages Issue: - If all the stages are deleted then the blank screen appears instead of shadow data. Cause: - Only `helpdesk.ticket` was being validated, but `helpdesk.stage.delete.wizard` was not included in the check. Fix: - The issue has been fixed by replacing active_model with default_team_id. task-4290529
This update resolves an issue where the 'Delivery Guide SII DTE 52' report for Chilean companies was missing withholding tax information. The fix ensures accurate reporting of both VAT and withholding taxes, aligning with Chilean tax regulations. This improves the reliability of financial reporting for deliveries.
Original PR description
Withholding tax information is missing when printing report 'Delivery Guide SII DTE 52 (CL)' from a delivery Steps to reproduce: - With a CL Company setup - Have a product with main 19% tax and a withholding tax - Create a SO with the product - Confirm - Open Delivery - Validate - Print menu > Delivery Guide SII DTE 52 (CL) Issue: Only VAT 19% tax is present in the report, withholding tax is missing (even if the total is correct) This occurs because the 'withholding' var is inside another dict Issue2: 'tax_name' is not present in the rendered data, so we need to add it Issue3: withholding amount will be shown without associated currency opw-4214377 Forward-Port-Of: odoo/enterprise#73926
This update corrects a technical issue that caused a traceback error when users interacted with the bank reconciliation feature in Odoo Enterprise. The fix ensures that the system correctly handles user selections, preventing errors and improving the overall stability of the accounting process. This resolves a minor disruption for users.
Original PR description
Fixing a traceback when selecting text, because the t-on-click was triggered but the target had no attribute. task: 4260301 Forward-Port-Of: odoo/enterprise#74509