This update streamlines how several Odoo screens reuse and adjust existing view settings. It makes future changes easier to maintain and reduces the chance that updates in a parent screen are missed in related screens.

This commit uses the `|` operator introduced in odoo/odoo#198551 to simplify fields' context and options in views. This improvement increases:
- readability: as it is more obvious what keys are added/modified by the XPath, and
- maintainability: as previously, any modifications to the parent view needed to be applied to the child views as well to have an effect.

This fixes spreadsheet filter side panels so they continue to open and collapse correctly after an internal naming change. It helps avoid small interface issues when users edit global filters in spreadsheets.

`collapsedAtInit` has been renamed to `isInitiallyCollapsed`

This fix makes an automated rental checkout test update date inputs more reliably. It helps prevent intermittent build warnings, improving confidence in release checks without changing the customer-facing shopping experience.

Before this commit, we had a non-deterministic warning on some runbot builds: see "shop_buy_rental_product" tour.

This is because we set the new value via the daterange picker and we need to trigger an "enter" event to force an input update.

runbot error: 161483
Related PR #82005

Social media post and comment formatting logic has been reorganized into a shared place to make the system easier to maintain. This cleanup improves consistency across Facebook, LinkedIn, Twitter, and YouTube integrations without changing the intended user experience.

- we ensure that the methods which involve formatting the tweet/comment are in
  the same modal.
- along the way, we also had a look at other different methods which we felt
  could could be moved at one place for better code organisation.

- also changed the names of the methods which were involved in formatting
  the comment/tweet. Made the names consistent.


Task-4184968

task-4577617 Forward-Port-Of: odoo/enterprise#80252

task-4577617

Forward-Port-Of: odoo/enterprise#80252

When we have a lot of data in the germany company we face a performance issue while exporting as zip file - modified the l10n_de_datev_export_to_zip function to search for the needed data rather that calling get lines again that improves the performance by 65%. - modified _format_column_values to add if options.get('export_mode') == 'file' not do formating to save time task-4502158 Forward-Port-Of: odoo/enterprise#81171

When we have a lot of data in the germany company we face a performance issue while exporting as zip file

- modified the l10n_de_datev_export_to_zip function to search for the needed data rather that calling get lines again that improves the performance by 65%.

- modified _format_column_values to add if options.get('export_mode') == 'file' not do formating to save time

 task-4502158

Forward-Port-Of: odoo/enterprise#81171

This commit ensures that sheet names in exported excel files are unique. The names may not be unique in case a composite report contains multiple section reports all having the same very long prefix. An example to that could be found in l10n_fr_reports: 1) IMB - Intermediate management balances 2) IMB - Intermediate management balances (2024) task-4678129 Forward-Port-Of: odoo/enterprise#82381 Forward-Port-Of: odoo/enterprise#82333

This commit ensures that sheet names in exported excel files are unique. The names may not be unique in case a composite report contains multiple section reports all having the same very long prefix. An example to that could be found in l10n_fr_reports: 1) IMB - Intermediate management balances
2) IMB - Intermediate management balances (2024)

task-4678129

Forward-Port-Of: odoo/enterprise#82381
Forward-Port-Of: odoo/enterprise#82333

…nning gantt Prior to this commit, flexible resources did not have their leaves reflected as gray cells in the planning gantt view. This was due to the work_intervals being ignored for the calculation of flexible resources availability. This commit adds measures to handle the leaves for flexible resources by setting a dummy attendance (which covers the whole length of the period in gantt interval), and then injects their leaves intervals. To replicate: 1. set timeoffs to a flexible res

…nning gantt

Prior to this commit, flexible resources did not have their leaves reflected as gray cells in the planning gantt view. This was due to the work_intervals being ignored for the calculation of flexible resources availability.

This commit adds measures to handle the leaves for flexible resources by setting a dummy attendance (which covers the whole length of the period in gantt interval), and then injects their leaves intervals.

To replicate:
1. set timeoffs to a flexible resource (whole day and half day)
2. open planning app
3. in the gantt view, the day in which the timeoff was set for a whole day should be fully grayed (in the default month granularity view)
4. when selecting only a day as the granularity of the gantt view, the day in which the timeoff was set for a half day should be half grayed. (from 00:00-12:00 in case of a morning timeoff, and from 12:00-24:00 in case of an afternoon timeoff)

ticket-id: 4492625
community: [198032](https://github.com/odoo/odoo/pull/198032)

Forward-Port-Of: odoo/enterprise#82274
Forward-Port-Of: odoo/enterprise#79532

eLearning uses server date when processing dashboard values, which causes a mismatch from the perspective of the user. This commit changes the source of "today" to use the user's timezone on the dashboard and actions, while keeping compute functions on the server date as these values should not change based on the timezone of the observer. opw-4411615 Forward-Port-Of: odoo/enterprise#82199 Forward-Port-Of: odoo/enterprise#80490

eLearning uses server date when processing dashboard values, which causes a mismatch from the perspective of the user. This commit changes the source of "today" to use the user's timezone on the dashboard and actions, while keeping compute functions on the server date as these values should not change based on the timezone of the observer.

opw-4411615

Forward-Port-Of: odoo/enterprise#82199
Forward-Port-Of: odoo/enterprise#80490

It is possible for a user to sync an existing whatsapp account and only after install some whatsapp bridge module. In that case the user will get an error as the template is created on the existing account with an existing name. We now prevent using the default value if a template with the same name already exists on it. task-4369979 Forward-Port-Of: odoo/enterprise#82260 Forward-Port-Of: odoo/enterprise#79786

It is possible for a user to sync an existing whatsapp account and only after install some whatsapp bridge module.

In that case the user will get an error as the template is created on the existing account with an existing name.

We now prevent using the default value if a template with the same name already exists on it.

task-4369979

Forward-Port-Of: odoo/enterprise#82260
Forward-Port-Of: odoo/enterprise#79786