This update removes an obsolete internal comment from the enterprise mail chatter code. It does not change how users interact with the system, but it helps keep the codebase clearer for future maintenance.

This update reorganizes the internal setup used for Documents spreadsheets, especially around collaboration handling and test data. It should make future spreadsheet changes easier and safer to validate, with little to no visible change for users.

This update adjusts how navigation and breadcrumb information is handled across spreadsheets, the enterprise web interface, and map views. It also prevents map views from failing when used outside the usual app flow, improving reliability in specialized setups.

This update makes a small change in the Documents spreadsheet area. The limited details suggest a minor adjustment intended to improve or correct how spreadsheet-related documents behave.

Steps to reproduce: - Create a new pricelist applied to all products and with a 20% discount - Go to the pricelist's configuration tab and select "Show public price & discount to the customer" - Create a new Rental Order and select a customer - Add a rental product to the Rental Order (e.g. Meeting Room) - Change the pricelist to the one created before - Click on "Update Prices" Result: A discount is calculated and wrongly applied to the rental product. Expected result: No discoun

Steps to reproduce:
- Create a new pricelist applied to all products and with a 20% discount
- Go to the pricelist's configuration tab and select "Show public price &
discount to the customer"
- Create a new Rental Order and select a customer
- Add a rental product to the Rental Order (e.g. Meeting Room)
- Change the pricelist to the one created before
- Click on "Update Prices"

Result:
A discount is calculated and wrongly applied to the rental product.

Expected result:
No discount should be applied to the rental product, because pricelists
rules shouldn't impact rental prices.

opw-2677974

Forward-Port-Of: odoo/enterprise#22852

Probably done to reduce the useless char because it's limited to 50 chars. But in usecase you send one product only, it is better with space. If you send more than one product, it will be cut in most case already... + add the picking in values used to render bpost label under _record key. It can be useful for small customization ;) Forward-Port-Of: odoo/enterprise#22851

Probably done to reduce the useless char because it's limited to 50 chars.
But in usecase you send one product only, it is better with space.
If you send more than one product, it will be cut in most case already...

+ add the picking in values used to render bpost label under _record key.
It can be useful for small customization ;)

Forward-Port-Of: odoo/enterprise#22851

In the case where a form view contains enough element to be able to be scrolled, we cannot add a new field in the scrolled area Because there is a css in web_enterprise: https://github.com/odoo/enterprise/blob/aabb60e7a89e2d0a62471b397b434e43a205e2f9/web_enterprise/static/src/legacy/scss/form_view.scss#L332-L334 Because of this Height jquery-ui does not detect the new element (draggable) because it is not in the (droppable) area because it has been scrolled up. opw-2695114 Forward-Po

In the case where a form view contains enough element to be able to be scrolled, we cannot add a new field in the scrolled area
Because there is a css in web_enterprise: 

https://github.com/odoo/enterprise/blob/aabb60e7a89e2d0a62471b397b434e43a205e2f9/web_enterprise/static/src/legacy/scss/form_view.scss#L332-L334

Because of this Height jquery-ui does not detect the new element (draggable) because it is not in the (droppable) area because it has been scrolled up.

opw-2695114

Forward-Port-Of: odoo/enterprise#22764

Since V15, qweb has changed its output format to Markup unicode. We need to adapt back the xml in utf-8 format to avoid an invalid request. opw-2706466 Forward-Port-Of: odoo/enterprise#22840

Since V15, qweb has changed its output format to Markup unicode. We need
to adapt back the xml in utf-8 format to avoid an invalid request.

opw-2706466

Forward-Port-Of: odoo/enterprise#22840

Accounts not included in the french P&L report Steps to reproduce: 1. Install the Accounting app 2. Install France accounting localization 3. Create journal entry in credit to the 656 account 4. The journal entry is not present in the french P&L report Solution: Add the missing accounts to the report OPW-2698868 Forward-Port-Of: odoo/enterprise#22832 Forward-Port-Of: odoo/enterprise#22753

Accounts not included in the french P&L report

Steps to reproduce:
1. Install the Accounting app
2. Install France accounting localization
3. Create journal entry in credit to the 656 account
4. The journal entry is not present in the french P&L report

Solution:
Add the missing accounts to the report

OPW-2698868

Forward-Port-Of: odoo/enterprise#22832
Forward-Port-Of: odoo/enterprise#22753

1. Create an invoice with "Immediate Payment" and an invoice date in the past for partner A in company with id 1 2. Create a similar invoice for partner B in another company 3. Go to follow-up level in both companies and be sure that all the levels uses the "Auto Execute" option 4. Wait for scheduled action "Account Report Followup; Execute followup" to run Action will be run for partner A but not for partner B because it takes into account only the first company opw-2671678 Forwar

1. Create an invoice with "Immediate Payment" and an invoice date in the
past for partner A in company with id 1
2. Create a similar invoice for partner B in another company
3. Go to follow-up level in both companies and be sure that all the
levels uses the "Auto Execute" option
4. Wait for scheduled action "Account Report Followup; Execute
followup" to run

Action will be run for partner A but not for partner B because it takes
into account only the first company

opw-2671678

Forward-Port-Of: odoo/enterprise#22812