Wednesday, March 12, 2025
3 changes · saas-17.4
Resolved issues and error corrections
This fixes a duplicate field shown in the Spanish TicketBAI multi-refund accounting view. Users will see a cleaner form with the same information displayed only once, reducing confusion without changing business processes.
Original PR description
The module is added in https://github.com/odoo/odoo/pull/191303 as a backport to https://github.com/odoo/odoo/pull/166533 in `saas-17.3`. In `saas-17.4` this module adds similar functionality from `l10n_es_edi_tbai`. The view is modified to avoid displaying the [same field](https://github.com/odoo/odoo/blob/6140fa87601af7a75b6cf1bd93132ebc471f9181/addons/l10n_es_edi_tbai/views/account_move_view.xml#L16) twice. The module will be merged in the upgrade to `18.0`. upgrade https://github.com/odoo/upgrade/pull/7341 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixed an error that could appear when viewing a project's raw data while the project stage feature was disabled. The duration tracking information is now only calculated when project stages are enabled, preventing the crash and keeping the project data view accessible.
Original PR description
Before this commit, a traceback is occurred when the user would like to see the raw data of a specific project and the project stage feature is disabled. This commit adds a group on `duration_tracking` field definition to be sure this field will only be computed when the project stage feature is enabled. opw-3709542 Closes #197321
The Planning app now handles deleted recurring shift series correctly when the scheduled job creates future shifts. This prevents the background process from crashing after users delete all repeats from one recurring shift while other recurring shifts still need processing.
Original PR description
To reproduce: - create two repeating planning.slot records, Shift A and Shift B - delete Shift A and all of its repeats - delete only the last repeat of Shift B - run the "Planning: generate next recurring shifts" scheduled action - Cron fails with "record is missing or deleted" error Problem: The function to create the repeat shifts (planning.recurrency _repeat_slot) iterates over recurrences and deletes them if there are 0 existing shifts linked to them (i.e. Shift A's reccurency). On a subsequent loop iteration, an attempt is made to access the company_id field of the recordset (self) which will now contain a deleted planning.recurrency record, causing the missing record error. Solution: Access the company_id field on the current iterated planning.recurrency record instead of the 'self' recordset. opw-4457844