Odoo Changelog — 2024-06-14

Friday, June 14, 2024

3 changes · saas-17.2

Improvements(2)

Enhancements to existing features

[IMP] portal: /my/counters performances

Coresaas-17.2portalMedium

Portal dashboard cards now avoid repeated counting during a user session once related records are known to exist. This reduces page refresh work and flickering, making the customer portal feel faster and more stable.

Original PR description

The counters are primarily used as boolean to determine whether or not
to display the card. Therefore, as soon as you have one record, we can
show the card without needing to recheck it later. In the worst-case
scenario, you might see a card pointing to an empty list view.
This approach helps us avoid recalculating whether there is a record for
this card on each refresh.

The approach is to cache the counter in the session as soon as there are
more than 0 records. This way, if there are no invoices but a sale order
is validated, the invoice counter will be recomputed, and you will see
the invoice card the next time. For the duration of the same session, we
won't recompute it and will always display the invoice card.
We only re-request the computation if the counter in the session was 0
or if we need to show the counter, as in this case, we want to display
the most precise number.

This approach will also avoid flickering when the view is updated.
Since we already know the count, we can display the card immediately
without waiting for the RPC callback. To further reduce flickering, we
have moved the spinner to the bottom, preventing the content from
shifting upwards once the loader disappears.

On another note, we've updated the policy for the parallel RPC requests
made to /my/counter. Instead of splitting the counter into 3 RPC calls,
we now allow 5 counters per RPC, with a maximum of three RPCs.

An update of the view portal.portal_docs_entry is required to benefit
from this cache for /my/counter,

#portal#performance#dashboard#user experience

[IMP] account{,_accountant}: allow grouping by Product (Category) in Deferred reports

PR #165592

Coresaas-17.2accountMedium

Deferred reports can now be grouped by product or product category, giving finance teams clearer ways to analyze deferred revenue and expenses. The underlying deferral generation remains grouped by account, preserving existing accounting behavior while improving report visibility.

Original PR description

We now allow grouping by other fields that account_id in the report, namely product_id, and product_category_id. However, for the deferral generation, we continue grouping by account_id.

task-id 3925943

https://github.com/odoo/enterprise/pull/62534

#deferred reports#product grouping#finance

Bug Fixes(1)

Resolved issues and error corrections

[FIX] spreadsheet: update o_spreadsheet to latest version

PR #169430

Coresaas-17.2spreadsheetMedium

This update brings the spreadsheet component to its latest maintenance version and fixes several user-facing issues. Users should see more reliable collaboration saving, better popover placement, corrected figure sizing with frozen panes, and improved find-and-replace range handling.

Original PR description

### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/7704cc416 [REL] 17.2.11 Task: 0 https://github.com/odoo/o-spreadsheet/commit/4bebc0608 [FIX] Figure: Fix container…

### Contains the following commits:

https://github.com/odoo/o-spreadsheet/commit/7704cc416 [REL] 17.2.11 Task: 0
https://github.com/odoo/o-spreadsheet/commit/4bebc0608 [FIX] Figure: Fix container size in presence of frozen panes Task: 3976086
https://github.com/odoo/o-spreadsheet/commit/83aec4b3b [FIX] collaborative: snapshot only when no pending changes Task: 0
https://github.com/odoo/o-spreadsheet/commit/f4989d00c [FIX] popover: popover position with scrollbar Task: 3981551
https://github.com/odoo/o-spreadsheet/commit/ff2141018 [FIX] data_validation: wrong popover position Task: 3981399
https://github.com/odoo/o-spreadsheet/commit/d0fcde5b5 [FIX] collaborative: snapshot when leaving spreadsheet Task: 3940465
https://github.com/odoo/o-spreadsheet/commit/a445f51e0 [FIX] FindAndReplaceSidePanel: Fix range update Task: 3972409

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: 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>

The counters are primarily used as boolean to determine whether or not to display the card. Therefore, as soon as you have one record, we can show the card without needing to recheck it later. In the worst-case scenario, you might see a card pointing to an empty list view. This approach helps us avoid recalculating whether there is a record for this card on each refresh. The approach is to cache the counter in the session as soon as there are more than 0 records. This way, if there are no invoices but a sale order is validated, the invoice counter will be recomputed, and you will see the invoice card the next time. For the duration of the same session, we won't recompute it and will always display the invoice card. We only re-request the computation if the counter in the session was 0 or if we need to show the counter, as in this case, we want to display the most precise number. This approach will also avoid flickering when the view is updated. Since we already know the count, we can display the card immediately without waiting for the RPC callback. To further reduce flickering, we have moved the spinner to the bottom, preventing the content from shifting upwards once the loader disappears. On another note, we've updated the policy for the parallel RPC requests made to /my/counter. Instead of splitting the counter into 3 RPC calls, we now allow 5 counters per RPC, with a maximum of three RPCs. An update of the view portal.portal_docs_entry is required to benefit from this cache for /my/counter,

We now allow grouping by other fields that account_id in the report, namely product_id, and product_category_id. However, for the deferral generation, we continue grouping by account_id. task-id 3925943 https://github.com/odoo/enterprise/pull/62534

### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/7704cc416 [REL] 17.2.11 Task: 0 https://github.com/odoo/o-spreadsheet/commit/4bebc0608 [FIX] Figure: Fix container size in presence of frozen panes Task: 3976086 https://github.com/odoo/o-spreadsheet/commit/83aec4b3b [FIX] collaborative: snapshot only when no pending changes Task: 0 https://github.com/odoo/o-spreadsheet/commit/f4989d00c [FIX] popover: popover position with scrollbar Task: 3981551 https://github.com/odoo/o-spreadsheet/commit/ff2141018 [FIX] data_validation: wrong popover position Task: 3981399 https://github.com/odoo/o-spreadsheet/commit/d0fcde5b5 [FIX] collaborative: snapshot when leaving spreadsheet Task: 3940465 https://github.com/odoo/o-spreadsheet/commit/a445f51e0 [FIX] FindAndReplaceSidePanel: Fix range update Task: 3972409 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: 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>