Friday, August 9, 2024
8 changes
2 changes
Resolved issues and error corrections
This fix stops Odoo from repeatedly retrying failed screens when several actions in the URL cannot be opened, preventing users from getting stuck in an endless error cycle. It also improves page reload behavior so previously opened dynamic screens can be restored correctly, making navigation more reliable.
Original PR description
- Open Accounting; - Open Bank Reconciliation; - Change the Company, to a company with not installed a chart of account. Before this commit, an infinity access error loop was raise. This occurs, because when an action is in an error on mounting on the action service, we try to mount the previous action, choose from a list of previously executed actions. The previous action, in this case, was also in error. In these case, it should go to the before last of the list, but as the previous one wasn't removed. It will try to mount it again, and create an infinity loop. opw-[4076702](https://www.odoo.com/web#id=4076702&view_type=form&model=project.task)
Duplicating records from list views now uses the same business context as duplicating from a form view. This prevents inconsistent copied records, such as rental sales orders missing rental-specific behavior when duplicated from a list.
Original PR description
Description of the issue/feature this PR addresses: - Adapting the fix for saas-17.2: https://github.com/odoo/odoo/pull/174137 It is found that context is never passed in '_duplicateRecords' function for list views, when making 'orm' calls from js side, while it is passed in 'duplicate' function of record.js, which is called when duplicating record from form view. 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
6 changes
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