Daily updates from Odoo
Friday, August 9, 2024
11 changes · 17.0
New functionality added to Odoo
This update introduces a new corporate tax report for Bangladesh operations. Users can now configure specific accounts in settings and automatically generate accounting entries with tax amounts directly from the report. The update also fixes a duplicate naming issue in the tax report.
Original PR description
[ADD] l10n_bd_reports: Create corporate tax report * Create new account tags * Create new corporate report * Create new fields in the settings to allow the user specifying accounts that should be used in the accounting entry * Create custom accounting entry button to create a move with the accounts specified by the user with amounts specified in the 'corporate tax amount' line in the corporate tax report NOTE: there is an issue with the name of the tax report, '(BD)' in the name is duplicate. So, Fixed it in this pr task-id#3974212 odoo-pr#https://github.com/odoo/odoo/pull/172254
Enhancements to existing features
The Kenya EDI system now accepts serial numbers with varying capitalization (e.g., "Odoo/pin/1" or "odoo/Pin/1" instead of only "ODOO/pin/1"). This change makes the system more user-friendly by accepting serial numbers regardless of how users capitalize the text when copying and pasting, reducing data entry errors.
Original PR description
We want to provide more flexibility to the user that instead of ODOO/pin/1 they did Odoo/pin/1 or odoo/Pin/1 as the serial number, we will still accept it. Because, while copying, you do not necessarily pay attention to capital letters or not.
This update improves how asset depreciation is calculated for Indian companies to comply with the Company Act of 2013. The depreciation calculation now uses the full original asset cost with a fixed 5% residual value, rather than the previous method. This ensures Indian businesses calculate depreciation correctly according to local regulations.
Original PR description
[IMP] l10n_in_reports, account_asset: Improve indian degressive depreciation according to the Company Act of 2013, depreciation should be calculated on the full cost 'original_value' and the residual value should be 5%, which is 5,000 in this casefor the indian case only so, it's not the general case. So, we need to overwrite the logic of the degressive depreication to adapt the desired flow. Now, We calculate the degressive amount by 'factor * current_value of asset' excluding 'salvage_value' task-id#3909619
A new EC sales list report has been added specifically for Denmark, allowing businesses to generate and export sales data in CSV format as required by Danish government regulations. This improvement enables Danish companies to easily comply with EC sales reporting requirements directly from Odoo.
Original PR description
Denmark government need a way to get ec sales. So now we have a report dedicated to denmark with an export to a CSV format task: 4080107 Backporting: https://github.com/odoo/enterprise/pull/58413/commits/d9f7ccdfd062fdc4e372951ff65a5f09046ad7b7
This update allows users to adjust the document reference length in XAF file exports for Dutch accounting reports. Previously, the fixed length exceeded what some accounting software could accept, preventing file imports. Now users can configure a system parameter to customize this length, making the exported files compatible with more third-party accounting systems.
Original PR description
Before this commit: Some softwares do not follow the specification. Our users cannot import the generated XAF file in other softwares because the docRef length is more than 35 characters. After this commit: We allow our users to create a system parameter to change the docRef length if they need to import the XAF file in another software. opw-3792115 opw-3829459 Forward-Port-Of: odoo/enterprise#68053 Forward-Port-Of: odoo/enterprise#66551
Resolved issues and error corrections
This fix resolves a visual problem where the MRP work order display showed a black box in dark mode instead of properly adapting to the theme. The update ensures the display looks correct and consistent whether users are working in light or dark mode by using Odoo's color scheme instead of Bootstrap's default styling.
Original PR description
Instead of using the `bg-white` class from boostrap, which is translated to black in dark-mode, make use of the color-scheme from odoo. This avoids having a mismatch between light and dark mode. Before (Dark / Light):  After (Dark / Light): 
This update fixes a missing required field in the Swiss payroll sickness insurance form view. The field was not properly configured in the system interface, which could have caused issues when users tried to enter sickness insurance information. This fix ensures the form displays and functions correctly for HR teams managing Swiss payroll.
Fixed an issue where appointment booking buttons with custom formatting would incorrectly route users to all appointments instead of the specific appointment type they selected. The fix ensures that styled buttons properly direct customers to their intended appointment type by accounting for nested HTML elements within the button.
Original PR description
Issue ----- When adding formating to an appointment button linked to a specific type of appointment, the button will lead to all appointments instead of just the specific type. Change ----- Since buttons can have custom formatting, this will add HTML elements inside the button element. Therefore, we need to take into account that the target of the event may not be the button itself. opw-4080512
This fix ensures that branch companies can properly access and report on unaffected earnings accounts from their parent company in general ledger and trial balance reports. When both a company and its branch are selected, the system now correctly sums the financial movements on the unaffected earnings account, providing accurate financial reporting across the organization.
Original PR description
On the general ledger and trial balance, the branch company needs to get access to the parent unaffected earning account. Also if a company and a branch is selected, we need to sum the moves on the unaffected earnings account. opw-3937063
Users with proper timesheet access permissions can now create invoices for sales orders with validated timesheets without encountering access errors. The fix adjusts permission checks to properly recognize authorized users, enabling the invoicing workflow to function correctly when timesheets are locked and validated.
Original PR description
## Issue: - A user with sufficient access rights to timesheet, ('User: all timesheets' or 'User: own timesheets only') cannot create an invoice for a sales order within a specific timesheet period,…
## Issue:
- A user with sufficient access rights to timesheet, ('User: all timesheets' or 'User: own timesheets only') cannot create an invoice for a sales order within a specific timesheet period, receiving the error: 'Timesheets before [PERIOD] are validated and cannot be modified.'
## Steps To Reproduce:
- Edit `Create on Order` of the `Service on Timesheets` product to be `Project & Task`.
- in settings:
- enable the `Lock Timesheets` option.
- set the invoicing policy for Timesheets to `validated timesheets only` .
- set the invoicing policy for Sales to 'invoice what is delivered'.
- Update the timesheet access for `Marc Demo` and set it as 'User: all timesheets'.
- Create a SO with `Service on Timesheets` as a product.
- On the related Task create a timesheet for period 01 May to 31 May and validate it.
- With Marc Demo click on Create an Invoice on the SO, for the same period notice The Access Error.
## Solution:
- in `check_if_allowed` I modified the condition to check if the current user is not a superuser.
opw-3965532
Forward-Port-Of: odoo/enterprise#65435This fix resolves issues with scanning GS1 barcodes that contain packaging information for tracked products. Previously, when scanning such barcodes, the system failed to retrieve packaging data and lot/serial numbers correctly. Now users can successfully scan and process tracked products with packaging using GS1 barcodes, improving warehouse operations efficiency.
Original PR description
Before this commit, when scaning a GS1 barcode containing a packaging for a tracked product and a lot, it doesn't work. This commit fixes two issues: 1. Get back packaging data (product and quantity) when a GS1 barcode is scanned; 2. Be able to find the lot/serial number when a GS1 barcode with no product but a packaging is scanned. Forward-Port-Of: odoo/enterprise#67947 Forward-Port-Of: odoo/enterprise#67727