Daily updates from Odoo
Monday, May 12, 2025
3 changes
Resolved issues and error corrections
This fix improves how accounting documents receive their official sequence numbers during large batch operations. It reduces database strain and avoids failures that could occur when many journal entries, assets, or batch payments are processed at the same time.
Original PR description
Creating many savepoints can lead to issues, not only in the current transaction, but also on other transactions from other connections on other databases[^1]. The `sequence.mixin` relies heavily on…
Creating many savepoints can lead to issues, not only in the current transaction, but also on other transactions from other connections on other databases[^1]. The `sequence.mixin` relies heavily on a unique constraint for giving a sequence without gaps[^2], which forces the use of savepoints because we expect the transaction to fail when assigning numbers with concurrent transactions. A previous commit removes savepoints created in a loop, which could happen when concurrency happens[^3], but there is still an issue when many records are getting a sequence number in the same transaction. This happens for instance when posting journal entries in batch (i.e. after an import), creating a `account.asset` in the past, or validating a batch payment with exchange differences. This commit is now locking the previous number, and then opening a new cursor in READ COMITTED in order to be able to see what other transactions did in the meantime. [^1]: https://github.com/odoo/odoo/pull/71395#issuecomment-851440042 [^2]: c45998c8368c6feb3d574d6d3d0ad064faf21679 [^3]: 10565c6968a5d0f285f93c4bdc610350999a88e3 Description of the issue/feature this PR addresses: 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
This update refreshes Odoo's spreadsheet engine and fixes several issues affecting pivots, formulas, charts, and sheet duplication. Users should see more reliable spreadsheet behavior, especially when working with pivot tables and date grouping.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/9b3634067 [REL] 18.0.27 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/9b3634067 [REL] 18.0.27 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0) https://github.com/odoo/o-spreadsheet/commit/56f15f64a [FIX] function: IF should not mutate its input [Task: 4783504](https://www.odoo.com/odoo/2328/tasks/4783504) https://github.com/odoo/o-spreadsheet/commit/c481408fe [FIX] pivot: handle undefined granularity [Task: 4742696](https://www.odoo.com/odoo/2328/tasks/4742696) https://github.com/odoo/o-spreadsheet/commit/fa27574d3 [FIX] pivot: add missing month granularity [Task: 4742696](https://www.odoo.com/odoo/2328/tasks/4742696) https://github.com/odoo/o-spreadsheet/commit/c4542385a [FIX] pivot: date dimension detection [Task: 4742696](https://www.odoo.com/odoo/2328/tasks/4742696) https://github.com/odoo/o-spreadsheet/commit/e2241428e [FIX] spreadsheet: add name to DUPLICATE_SHEET [Task: 4640070](https://www.odoo.com/odoo/2328/tasks/4640070) https://github.com/odoo/o-spreadsheet/commit/58009a9d2 [FIX] pivot: cannot use pivot formula inside its range [Task: 3986479](https://www.odoo.com/odoo/2328/tasks/3986479) https://github.com/odoo/o-spreadsheet/commit/c48960456 [FIX] chart: can `UPDATE_CHART` on a non-chart figure [Task: 4775605](https://www.odoo.com/odoo/2328/tasks/4775605) https://github.com/odoo/o-spreadsheet/commit/6b78636b2 [FIX] GridComposer: limit the composer size [Task: 4686816](https://www.odoo.com/odoo/2328/tasks/4686816) Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com> Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com> Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com> Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com> Co-authored-by: Mehdi Rachico (mera) <mera@odoo.com> Co-authored-by: Florian Damhaut (flda) <flda@odoo.com> Co-authored-by: Rémi Rahir (rar) <rar@odoo.com> Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com> Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>
Updating a pivot table from the spreadsheet side panel no longer removes the user's selected column sorting. This preserves the expected report order after changes such as adjusting filters, avoiding confusion and rework.
Original PR description
This commit fixes the fix 10f8722f5e7 🙈 Steps to reproduce: - go to a pivot view - sort a measure column - insert the pivot into a spreadsheet - open the side panel - update anything (e.g. the domain) => the sorting is dropped. What happened? Why didn't 10f8722f5e7 fixed the issue? I think I originally investigated and fixed the issue in master (or at least in saas-18.1+). Then I just blindly backported the fix to 18.0. BUT ! `sortedColumn.measure` changed in saas-18.1 with cb229b4a2ef247 After this commit commiit, it's the measure id, but it was the field name before. Task: 4746057