Video calls are now better protected when a user closes a browser tab. If another available browser tab is open, the system will try to recover the ongoing call there, reducing accidental call interruptions.

**Current behavior before PR:**
Closing a browser tab with an ongoing video call terminates it.

**Desired behavior after PR is merged:**
If another available browser exists, it will attempt to recover the call.

Task-3244140

[COMMUNITY PR](https://github.com/odoo/odoo/pull/174201)

Users opening Documents from a project are now taken straight to that project's folder, making it faster to find and upload project files. Folder navigation is also corrected so users can move through document folders as expected.

Open the documents app directly in the project's folder allows quicker access to documents and upload.
We also correct view contexts to show folders to allow navigation.

(Setting `action_id` to `False` for updating existing records, see `check_only_one_action_defined`)

Task-4216195

This fixes an issue that could cause Chilean point-of-sale receipts to fail when the restaurant POS module was not installed. The change makes the receipt customization work reliably for standard POS setups as well.

XPath was wrongly set, l10n_cl_edi_pos was trying to xpath a node only present in pos_restaurant module, if that one wasn't installed it would crash.

Currently the EC Sales List menuitem is not visible when only installing `l10n_fr_reports` (and no other localization activating the item). To reproduce it you need to install `l10n_fr_reports` on a database where the item is not already visible. (It does not work on the runbot.) Forward-Port-Of: odoo/enterprise#71021 Forward-Port-Of: odoo/enterprise#70723

Currently the EC Sales List menuitem is not visible when only installing `l10n_fr_reports` (and no other localization activating the item).

To reproduce it you need to install `l10n_fr_reports` on a database where the item is not already visible. (It does not work on the runbot.)

Forward-Port-Of: odoo/enterprise#71021
Forward-Port-Of: odoo/enterprise#70723

In the payment report, a space was missing between the VAT label and the span "Emitter Acc. Ben.". In order to don't rely on spaces, a ps-1 class was added in both "Emitter Acc. Ben." and "Emitter Acc. Ord.". --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#69259 Forward-Port-Of: odoo/enterprise#53722

In the payment report, a space was missing between the VAT label and
the span "Emitter Acc. Ben.". In order to don't rely on spaces, a ps-1
class was added in both "Emitter Acc. Ben." and "Emitter Acc. Ord.".

---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Forward-Port-Of: odoo/enterprise#69259
Forward-Port-Of: odoo/enterprise#53722

The purpose of this PR is to make it easier to use overlays in the editor. 1. Clarify the createOverlay API. ================================ Before, we mixed up the positioning hook options and the EditorOverlay props. After, put all the positioning options in the positionOptions props and move the sequence to the last param, which corresponds to the overlay system options. 2. Automatically manage the close at pointerdown. ================================================= Before, t

The purpose of this PR is to make it easier to use overlays in the editor.

1. Clarify the createOverlay API.
================================
Before, we mixed up the positioning hook options and the EditorOverlay props.
After, put all the positioning options in the positionOptions props
and move the sequence to the last param, which corresponds to the overlay
system options.

2. Automatically manage the close at pointerdown.
=================================================
Before, the logic for closing overlays outside the overlay was duplicated
in each component use by createOverlay.
After, the overlay editor is responsible for closing overlays when a pointerdown
occurs outsite of the overlay. You can disable this functionality with the closeOnPointerdown=‘false’ props.

3. Managing setSelections when the selection is not in the editable
===================================================================
For example, the selection is in the input of an overlay.
From this commit, when you call setSelection, if the selection is not in
the editable, you no longer force the selection to be moved into the editable,
you just update the activeSelection. When you want to force the restoration
of the selection in the editable, for example when you close an overlay,
you call the focusEditable function.
This change makes it possible to call functions that manipulate the selection
from the outside without having to refocus in the editor.

Forward-Port-Of: odoo/enterprise#70534

Steps: - create a bom for Product A with the following component: Semifinished B, ratio 1.0 - create a bom for Semifinished B with the following component: Raw C, ratio 1.0 - add A with its bom, B should be created automatically after adding A - add B (even if already present) with its bom, C should be created automatically after adding B - input a forecasted demand of 1 for A (the period doesn't matter) - there should be an indirect demand of 1 for B and C - input a forecasted demand of

Steps:
- create a bom for Product A with the following component: Semifinished B, ratio 1.0
- create a bom for Semifinished B with the following component: Raw C, ratio 1.0
- add A with its bom, B should be created automatically after adding A
- add B (even if already present) with its bom, C should be created automatically after adding B
- input a forecasted demand of 1 for A (the period doesn't matter)
- there should be an indirect demand of 1 for B and C
- input a forecasted demand of 4 for B in the same period
- there should now be an indirect demand of 5 for C

Issue:
The indirect demand of C stays at 1 because the code bypasses the intermediate forecasted demand if there's an indirect demand from a level above

Fix:
Store the indirect demand at ratio in `subproduct_indirect_demand`
If `subproduct_indirect_demand` is different from `ratio * forecast_values['replenish_qty']`, substract it from the entire `replenish_qty` for the corresponding period when adding to `indirect_demand_qty`.

Cases:
`subproduct_indirect_demand` == `ratio * forecast_values['replenish_qty']`:
- base case, there's only indirect demand for B, skip
- there's forecasted demand on B and an equal reduction on the manual replenish qty, skip => the demand is reported to the next period as normal
- there's forecasted demand on B and a max to replenish qty that nullifies it, skip => same as above

`subproduct_indirect_demand` < `ratio * forecast_values['replenish_qty']`:
- base case, there's no indirect demand, proceed
- there's additional forecasted demand for B, proceed => add `(ratio * forecast_values['replenish_qty']) - subproduct_indirect_demand` to the `indirect_demand_qty` dict
- there's additional replenish qty for B, proceed => the additional qty is set on the first day of the period

`subproduct_indirect_demand` > `ratio * forecast_values['replenish_qty']`:
- there's a manually input `replenish_qty` that is inferior to the indirect demand, proceed => the parent_date is set at the end of the current period in case of lead time to prevent negative replenish qty on the period before

Forward-Port-Of: odoo/enterprise#70232

This commit adapts documents tests to changes made in https://github.com/odoo/odoo/pull/180776 Forward-Port-Of: odoo/enterprise#70924 Forward-Port-Of: odoo/enterprise#70795

This commit adapts documents tests to changes made in https://github.com/odoo/odoo/pull/180776

Forward-Port-Of: odoo/enterprise#70924
Forward-Port-Of: odoo/enterprise#70795

Follow-ups of 4576bcac. Task-3373836 Forward-Port-Of: odoo/enterprise#70668

Follow-ups of 4576bcac.

Task-3373836

Forward-Port-Of: odoo/enterprise#70668

Steps to reproduce: - Install Timesheet when on Time Off - Timesheet > Start > Input a project in the header - Try to input a task Unlike in previous versions, the tasks are not filtered to only show the belonging to the selected project. This happens because timesheet_grid_holidays adds a value to the fieldInfo domain, having a non empty domain means it is picked over field.domain, which contains the necessary filters otherwised used on tasks. opw-4204658 Forward-Port-Of: odoo/enterpr

Steps to reproduce:
- Install Timesheet when on Time Off
- Timesheet > Start > Input a project in the header
- Try to input a task

Unlike in previous versions, the tasks are not filtered to only show the belonging to the selected project. This happens because timesheet_grid_holidays adds a value to the fieldInfo domain, having a non empty domain means it is picked over field.domain, which contains the necessary filters otherwised used on tasks.

opw-4204658

Forward-Port-Of: odoo/enterprise#70749

The PR https://github.com/odoo/enterprise/pull/66908 has introduced some problems in the way the studio navbar is styled in dark mode: mainly its menu items are not visible. Here we adapt some variables to have them visible again and have a suitable style on on hover. Forward-Port-Of: odoo/enterprise#71029

The PR https://github.com/odoo/enterprise/pull/66908 has introduced some problems in the way the studio navbar is styled in dark mode: mainly its menu items are not visible.
Here we adapt some variables to have them visible again and have a suitable style on on hover.

Forward-Port-Of: odoo/enterprise#71029

Previously, it was considered that a company needed to allow the generation of purchase orders for inter-company transactions in order to allow the sync between deliveries made to it and its own receptions. This implied that a company not allowing automated purchases to be made on itself couldn't sync its receipts with a sale order generated another company following a purchase to it, which is quite confusing user-wise. To avoid that, we allow the sync regardless of the selected options fo

Previously, it was considered that a company needed to allow the generation of purchase orders for inter-company transactions in order to allow the sync between deliveries made to it and its own receptions.

This implied that a company not allowing automated purchases to be made on itself couldn't sync its receipts with a sale order generated another company following a purchase to it, which is quite confusing user-wise.

To avoid that, we allow the sync regardless of the selected options for automated Purchase / Sale Order generation.

Task-4207009

Forward-Port-Of: odoo/enterprise#70740

*documents_account, documents_hr_recruitment, l10_in_hr_payroll,l10n_uy_edi before this commit, few tree tags are left over without changing into list tag in this commit: 4ca79b1#diff-e8da39382dbb141dfbfcec84a5a4365734015a25cd3ed94004f7eb7daa7e7ab0R12 after this commit, all tree tag will be converted 'into list tag Forward-Port-Of: odoo/enterprise#71002

*documents_account, documents_hr_recruitment,
l10_in_hr_payroll,l10n_uy_edi

before this commit, few tree tags are left over without changing into list tag in this commit: 4ca79b1#diff-e8da39382dbb141dfbfcec84a5a4365734015a25cd3ed94004f7eb7daa7e7ab0R12

after this commit, all tree tag will be converted 'into list tag

Forward-Port-Of: odoo/enterprise#71002

`test_loan_import_amortization_schedule` was failing because of a missing `freeze_time` which has now been added along with hard-coded dates instead of relative dates which are more prone to errors. runbot errors: 100079 100342 Forward-Port-Of: odoo/enterprise#71030

`test_loan_import_amortization_schedule` was failing because of a missing `freeze_time` which has now been added along with hard-coded dates instead of relative dates which are more prone to errors.

runbot errors: 100079 100342

Forward-Port-Of: odoo/enterprise#71030

The problem was that the date picker was disabled when we have Use Existing ones only enabled, but it should be enabled when "Use Existing ones" is checked or "Create New" in the config of "Lots/Serial Numbers". Steps to reproduce: - add a product tracked by lots and have also enabled expiration dates - inventory Receipts configuration - in general, check both options "Use Existing ones" and "Create New" under "Lots/Serial Numbers" - now if you receive product in barcode app, you

The problem was that the date picker was disabled when we have Use Existing ones only enabled, but it should be enabled when "Use Existing ones" is checked or "Create New" in the config of "Lots/Serial Numbers".

Steps to reproduce:

- add a product tracked by lots and have also enabled expiration dates

- inventory Receipts configuration

- in general, check both options "Use Existing ones" and "Create New" under "Lots/Serial Numbers"

- now if you receive product in barcode app, you will see expiration date of the lots disbaled

opw-4086325

Forward-Port-Of: odoo/enterprise#70913
Forward-Port-Of: odoo/enterprise#68008

**Version:** - saas-17.4 **Steps to reproduce:** - activate debug mode - go to template with no sign record - click on the "signed document" state button or option from the template kanban **Issue:** - it was giving traceback when clicking on "signed documents". **Cause:** - an UncaughtPromiseError was triggered due to an undefined 'noContentHelp' prop in the SignActionHelper component. **Solution:** - removed the 'noContentHelp' prop from the SignActionHelper component to pre

**Version:**
- saas-17.4

**Steps to reproduce:**
- activate debug mode
- go to template with no sign record
- click on the "signed document" state button or option from the template kanban

**Issue:**
- it was giving traceback when clicking on "signed documents".

**Cause:**
- an UncaughtPromiseError was triggered due to an undefined 'noContentHelp' prop in the SignActionHelper component.

**Solution:**
- removed the 'noContentHelp' prop from the SignActionHelper component to prevent the validation error as it is not used at anywhere.

task-4098729

Forward-Port-Of: odoo/enterprise#68021

To reproduce: 1) Create two companies, with different currencies, make them both active in the selector 2) Open the P&L 3) Create a new financial budget 4) Try to add an amount to some account for this budget ==> Traceback. This happens because the currency table is not initialized. When modifying a manual value, a different public function is called server-side than when rendering the report ; we need to initialize it there as well. Forward-Port-Of: odoo/enterprise#71022

To reproduce:

1) Create two companies, with different currencies, make them both active in the selector 2) Open the P&L
3) Create a new financial budget
4) Try to add an amount to some account for this budget

==> Traceback.

This happens because the currency table is not initialized. When modifying a manual value, a different public function is called server-side than when rendering the report ; we need to initialize it there as well.

Forward-Port-Of: odoo/enterprise#71022

This commit fix a test that was not testing a real flow due to a lack of uuid on the order lines. It is now re-written. Related: https://github.com/odoo/odoo/pull/181858 Forward-Port-Of: odoo/enterprise#70925

This commit fix a test that was not testing a real flow due to a lack of uuid on the order lines. It is now re-written.

Related: https://github.com/odoo/odoo/pull/181858

Forward-Port-Of: odoo/enterprise#70925

Fixes for multiple things related to extract status header: - Fix split translation string by choosing a generic term - On smaller displays, the header was not taking up the full width - Added check_status_loading to disable button when rpc is loading - Remove header in expense when the user refreshes a extracted document - Sync record props when switching between documents or manually requesting extraction Forward-Port-Of: odoo/enterprise#70498

Fixes for multiple things related to extract status header:
- Fix split translation string by choosing a generic term
- On smaller displays, the header was not taking up the full width
- Added check_status_loading to disable button when rpc is loading
- Remove header in expense when the user refreshes a extracted document
- Sync record props when switching between documents or manually requesting extraction

Forward-Port-Of: odoo/enterprise#70498

Steps to reproduce: - Install the helpdesk_sale_timesheet module. - Create two helpdesk teams (e.g. VIP Support and Customer Care). - Enable time billing and timesheets for the VIP Support team only. - In the portal view of tickets observe that the "Time Spent" label is missing Issue: - In the portal view you will see the 'Time Spent' label missing. Cause: - In the portal view of tickets the 'Time Spent' label is missing because when data is grouped (e.g. by stage, assignee, or t

Steps to reproduce:
- Install the helpdesk_sale_timesheet module.
- Create two helpdesk teams (e.g. VIP Support and Customer Care).
- Enable time billing and timesheets for the VIP Support team only.
- In the portal view of tickets observe that the "Time Spent" label is missing

Issue:
- In the portal view you will see the 'Time Spent' label missing.

Cause:
- In the portal view of tickets the 'Time Spent' label is missing because when data is grouped (e.g. by stage, assignee, 
  or team) it will check for the first group of tickets. It evaluates group in ascending order and if `use_helpdesk_sale_timesheet` is set to false for the first group the 'Time Spent' label will disappears even if it's enabled for other group.

Fix:
- In this commit we will check the `use_helpdesk_sale_timesheet` field for every ticket in the list. If it is set to true for any ticket the "Time Spent" label will be displayed; otherwise it will remain hidden.

limitation :
- In this case we need to add the list because removing `any` from the condition would violating our stability policy.

task-4058210

Forward-Port-Of: odoo/enterprise#70969
Forward-Port-Of: odoo/enterprise#69331

… nor dashboard Steps to reproduce: * Install hr and spreadsheet (not documents nor dashboard!) * Try to link a menu to spreadsheet * Click confirm => Boom Task: 4134791 Forward-Port-Of: odoo/enterprise#69280

… nor dashboard

Steps to reproduce:
* Install hr and spreadsheet (not documents nor dashboard!)
* Try to link a menu to spreadsheet
* Click confirm => Boom

Task: 4134791

Forward-Port-Of: odoo/enterprise#69280

Some specific flows could lead to a break in the hash chain, due to a missing check that ensure no aml are deleted. This check is added, as well as a nicer error message in the flow that would cause the issue to guide the user. Forward-Port-Of: odoo/enterprise#70869

Some specific flows could lead to a break in the hash chain, due to a missing check that ensure no aml are deleted.

This check is added, as well as a nicer error message in the flow that would cause the issue to guide the user.

Forward-Port-Of: odoo/enterprise#70869

Steps to reproduce: - Download 'Project' and 'Subscription' - Create a product with: -- Product type: 'Service' -- Create on order: 'Task' -- Project: Pick any -- Recurring checkbox must not be ticked - Subscription > New > Add any recurring product > Confirm - Create invoice > Confirm invoice > Back to subscription - Upsell > Add your task creation product > Confirm - The project is linked but no task is created The ability to create tasks from upsell orders was disabled in cbbc70f7

Steps to reproduce:
- Download 'Project' and 'Subscription'
- Create a product with: -- Product type: 'Service'
-- Create on order: 'Task'
-- Project: Pick any
-- Recurring checkbox must not be ticked
- Subscription > New > Add any recurring product > Confirm
- Create invoice > Confirm invoice > Back to subscription
- Upsell > Add your task creation product > Confirm
- The project is linked but no task is created

The ability to create tasks from upsell orders was disabled in cbbc70f73e6fe9e29e27dea4415e20a262bbdf82.
According to the commit message, this was done because upsell orders prorate the price of subscriptions accoding to the time until next invoice relative to the subscription's recurrence (i.e. if the upsell is created halfway through the recurrence it is discounted by 50% etc...). Since we do not have a way to prorate tasks it is marked as a technical limitation.

This however does not need to extend to non-recurring products on subscription sale orders as they are not prorated.

opw-4114049

Forward-Port-Of: odoo/enterprise#69794

Adds a test for the counterpart in community side. Checks that a delivery in the 'Inter-Company transit' location is properly shown as "delivered quantity" in the SO form. See odoo/odoo#181412 Task-4207132 Forward-Port-Of: odoo/enterprise#70903 Forward-Port-Of: odoo/enterprise#70663

Adds a test for the counterpart in community side. Checks that a delivery in the 'Inter-Company transit' location is properly shown as "delivered quantity" in the SO form.

See odoo/odoo#181412

Task-4207132

Forward-Port-Of: odoo/enterprise#70903
Forward-Port-Of: odoo/enterprise#70663

This commit adds the missing neutralization necessary for the pos_urban_piper module introduced in [1] The purpose of the standard neutralization framework is to allow us to create database copies that will not interact with external systems in ways that could impact the production database (or if it is not possible to prevent the interactions, make sure that they are benign or won't result in actual changes), or impact the customers of the operator of the production database. This is mainly u

This commit adds the missing neutralization necessary for the
pos_urban_piper module introduced in [1]

The purpose of the standard neutralization framework is to allow us to
create database copies that will not interact with external systems in
ways that could impact the production database (or if it is not possible
to prevent the interactions, make sure that they are benign or won't
result in actual changes), or impact the customers of the operator of
the production database.

This is mainly useful to allow safe support investigation on database
duplicates.

[1] https://github.com/odoo/enterprise/pull/66733

Forward-Port-Of: odoo/enterprise#70803

### Steps to reproduce: - Have two companies: COMP1, COMP2 - In the settings Enable Multi-step routes Prior to 17.2: - Inventory > Configuration > Warehouse Management > Locations - Unarchive: Virtual Locations/Inter-company transit and set is Return Locations - With COMP1: Create and confirm a PO with COMP2 as vendor for 10 units of a storable product - Validate the receipt and return. Select the Virtual Locations/Inter-company transit as return location and validate #### > On the POL

### Steps to reproduce:

- Have two companies: COMP1, COMP2
- In the settings Enable Multi-step routes Prior to 17.2:
- Inventory > Configuration > Warehouse Management > Locations
- Unarchive: Virtual Locations/Inter-company transit and set is Return Locations
- With COMP1: Create and confirm a PO with COMP2 as vendor for 10 units of a storable product
- Validate the receipt and return. Select the Virtual Locations/Inter-company transit as return location and validate
#### > On the POL the received quantity went from 10 to 20 rather than 0

#### Note:

Starting from 17.2, the Inter-company transit location is the default location destination of the return rather than (Partner/Vendor). It also changed its reference to `stock_location_inter_company` so that the fix should be adapted in that version.

### Cause of the Issue:

Currently, the qty_received is computed with respect to moves linkes to the POL. However, a move is flagged as a return only if the usage of its destination supplier (dropshipping and subcontracting flow excluded): https://github.com/odoo/odoo/blob/f494496b5142af23ee46ce249a1063f9d6caf403/addons/purchase_stock/models/stock_move.py#L247-L249 and if it is not flagged a return, its quantity is counted positively rather than negatively in the received quantity:
https://github.com/odoo/odoo/blob/f494496b5142af23ee46ce249a1063f9d6caf403/addons/purchase_stock/models/purchase.py#L348-L370

opw-4190647

Forward-Port-Of: odoo/enterprise#70871
Forward-Port-Of: odoo/enterprise#70376

Steps to reproduce - Create a horizontal group - open the trial balance -> Traceback Cause of the issue: a None value is set in the 'no_format' key of a line of the report. Forward-Port-Of: odoo/enterprise#70561

Steps to reproduce
 - Create a horizontal group
 - open the trial balance -> Traceback

Cause of the issue:
a None value is set in the 'no_format' key of a line of the report.

Forward-Port-Of: odoo/enterprise#70561

Issr and LEI nodes were added twice, because they were handled both in the generic ISO20022 code and the SEPA Credit Transfer override. Forward-Port-Of: odoo/enterprise#70756

Issr and LEI nodes were added twice, because they were handled both in the generic ISO20022 code and the SEPA Credit Transfer override.

Forward-Port-Of: odoo/enterprise#70756

[IMP] account_sepa_direct_debit: better sequence of error messages The check validating the collection date was made before we've checked all mandates are in the right state, yet it depended on the mandates to check the minimum collection date available for this batch. We now make it so we first check all the mandates are valid, for usability. =================================================== [FIX] account_sepa_direct_debit: Don't crash when validating a batch when the company

[IMP] account_sepa_direct_debit: better sequence of error messages
    
    The check validating the collection date was made before we've checked all mandates are in the right state, yet it depended on the mandates to check the minimum collection date available for this batch. We now make it so we first check all the mandates are valid, for usability.

===================================================

[FIX] account_sepa_direct_debit: Don't crash when validating a batch when the company has no creditor identifier

A check for that already existed in validate_batch, raising an error, but it wasn't called in time, and this caused a traceback because the super call had been moved at the beginning of the function.

===================================================

[IMP] account_sepa_direct_debit: clearer error message

===================================================

    [FIX] account_sepa_direct_debit: don't crash when trying to generate a batch containing a single SDD payment without mandate
    
    To reproduce:
    
    1) Create a payment for some new partner, using SEPA Direct Debit. Make sure no mandate exists for this partner.
    2) Add the payment created in 1 into a new batch. It must be the only payment in it
    3) Try validating the batch
    ====> Traceback
    
    This is because the query checking which mandates are used for the first time receives an empty tuple for its "mandate_ids" parameter. SQL tries to run "... IN ()", which crashes.
    
    After fixing this bug, the same flow still crashes because we're trying to call max() on an empty sequence in validate_batch in order to compute the pre_notification_period. We fix that by adding a new check in order to redirect the user in case some payments of the batch are missing a mandate.

Forward-Port-Of: odoo/enterprise#70923

…in the control panel When saving a new favourire view from the control panel a traceback would appear. It was because the domain was not parsed correctly in search_model.js when calling the getDomain method from the _getIrFilterDescription method. It was not parsed correctly because 2 parameters given to the method were lost because the getDomain method was overwritten in HighlightProjectTaskSearchModel. After passing the parameters to the super call inside the overwritten getDomain me

…in the control panel

When saving a new favourire view from the control panel a traceback would appear.

It was because the domain was not parsed correctly in search_model.js when calling the getDomain method from the _getIrFilterDescription method. It was not parsed correctly because 2 parameters given to the method were lost because the getDomain method was overwritten in HighlightProjectTaskSearchModel.

After passing the parameters to the super call inside the overwritten getDomain method, the traceback is fixed.

task-4207512

Forward-Port-Of: odoo/enterprise#70624

Some were missing, some terms were added after the original pot push due to delayed freeze time. COM PR: https://github.com/odoo/odoo/pull/181615 Forward-Port-Of: odoo/enterprise#70779

Some were missing, some terms were added after the original pot push due to delayed freeze time.

COM PR: https://github.com/odoo/odoo/pull/181615

Forward-Port-Of: odoo/enterprise#70779

This fixes issues that arose in 6aa473d, including: - Payments creations in batch from the list view do not handle the multiple partners case - The blue "Valid mandate available" banner does not show when you're not already using the SDD payment method Forward-Port-Of: odoo/enterprise#70597

This fixes issues that arose in 6aa473d, including:
 - Payments creations in batch from the list view do not handle the multiple partners case
 - The blue "Valid mandate available" banner does not show when you're not already using the SDD payment method

Forward-Port-Of: odoo/enterprise#70597

When validation an order in a Chilean shop, the date is not show on the receipt. Steps to reproduce: ------------------- * Change the company for the Chilean one **CL Company** * Go to the **Point of sale** App * Open shop session * Make and order and validate it > Observation: The date is not reported on the receipt Why the fix: ------------ Commit https://github.com/odoo/enterprise/commit/1ce4eaa025426354c640e6e6c69269b1e6b2c7d1 moved the date on receipt in the header for the chi

When validation an order in a Chilean shop, the date is not show on the receipt.

Steps to reproduce:
-------------------
* Change the company for the Chilean one **CL Company**
* Go to the **Point of sale** App
* Open shop session
* Make and order and validate it
> Observation: The date is not reported on the receipt

Why the fix:
------------
Commit https://github.com/odoo/enterprise/commit/1ce4eaa025426354c640e6e6c69269b1e6b2c7d1 moved the date on receipt in the header for the chilean localization.

Header uses the data from `props.headerData`
https://github.com/odoo/odoo/blob/5f748c9d5731fe2e7e519ee9625da25e2bb219bc/addons/point_of_sale/static/src/app/navbar/cash_move_popup/cash_move_receipt/cash_move_receipt.xml#L6

The date field in `headerData` is computed in `getReceiptHeaderData` https://github.com/odoo/enterprise/blob/923dfe962b714797ee41e8f7beed2cb2d6df7048/l10n_cl_edi_pos/static/src/overrides/models/pos_store.js#L48

However, this commit https://github.com/odoo/odoo/commit/5cb7639160cef5401ada8cdde5a5522d8d29c9a9 removed the field `receiptDate` on the pos order. We thus use the same logic to set the date in `headerData`.

opw-4136943

Forward-Port-Of: odoo/enterprise#70833
Forward-Port-Of: odoo/enterprise#70131

…ights The setup of the password from a related field would throw errors to user with accountant rights but no administration (settings) rights. This showed other access rights problems with the SBR implementation. The way we want to work with this is: an accountant without settings rights can set up the password through the wizard if no password is stored on the company (for databases that didn't start SBR with the status info module). Once the password is set and is correct (it is the ri

…ights

The setup of the password from a related field would throw errors to user with accountant rights but no administration (settings) rights. This showed other access rights problems with the SBR implementation.

The way we want to work with this is: an accountant without settings rights can set up the password through the wizard if no password is stored on the company (for databases that didn't start SBR with the status info module). Once the password is set and is correct (it is the right one for the certificate), it shouldn't ask the user to put it again and is thus hidden in the wizard.

ticket-4024344

Forward-Port-Of: odoo/enterprise#66096

Purpose ======= Skip user permission check, when calling `_action_update_access` in SUDO, like it has been done for `_action_update_members` Forward-Port-Of: odoo/enterprise#70724

Purpose
=======
Skip user permission check, when calling `_action_update_access` in SUDO, like it has been done for `_action_update_members`

Forward-Port-Of: odoo/enterprise#70724

The commit prevents the Documents portal from crashing when portal users try to preview a document. We prevent the client from raising an error when trying to access an undefined available embedded actions records (not available for portal users.) task-3373836 Forward-Port-Of: odoo/enterprise#70667

The commit prevents the Documents portal from crashing when portal users try to preview a document.

We prevent the client from raising an error when trying to access an undefined available embedded actions records (not available for portal users.)

task-3373836

Forward-Port-Of: odoo/enterprise#70667

After this commit: ----------------------- - A sequence number has been introduced to manage floating orders. - We display the platform ID instead of the order OTP because the platform ID is consistent across all providers, while the OTP information may vary depending on the provider. - A new pos_urban_piper_swiggy module added to support Swiggy integration with Urbanpiper. Task-4195863 Forward-Port-Of: odoo/enterprise#70433

After this commit:
-----------------------
- A sequence number has been introduced to manage floating orders.
- We display the platform ID instead of the order OTP because the platform ID is
consistent across all providers, while the OTP  information may vary depending
on the provider.
- A new pos_urban_piper_swiggy module added to support Swiggy
integration with Urbanpiper.

Task-4195863

Forward-Port-Of: odoo/enterprise#70433

The Modelo 303 has been updated according to [Orden HAC/819/2024] of July 30, 2024. Changes starting from periods 09 and 3T 2024: --------------------------------------------- * Box 108 was added to allow for manually entering those rectifications for which there is no specific box in the form. * Box 111 was added to differentiate refund requests that arise from the application of tax regulations from those that may correspond to a request for undue income. * 3 boolean fields were added i

The Modelo 303 has been updated according to [Orden HAC/819/2024] of July 30, 2024.

Changes starting from periods 09 and 3T 2024:
---------------------------------------------
* Box 108 was added to allow for manually entering those rectifications for which there is no specific box in the form.
* Box 111 was added to differentiate refund requests that arise from the application of tax regulations from those that may correspond to a request for undue income.
* 3 boolean fields were added in case we are submitting a rectification to indicate that:
  - we want to cancel/modify the direct debit made before;
  - the rectification is due to a discrepancy with administrative criteria;
  - the rectification is due to another reason.

Changes starting from periods 10 and 4T 2024:
---------------------------------------------
* Boxes 153, 154 and 155 were changed to reflect the updated VAT rate of 7.5%.
* Boxes 16, 17 and 18 were changed to reflect the updated Rec. Eq. rate of 1%.
* Boxes 165 to 170 were added to report the new VAT rate of 2% and the new Rec. Eq. rate of 0.26%.
* Box 27 was updated to take into account the new boxes 167 and 170 in its computation.

(See also [Real Decreto-ley 4/2024])

The BOE file export was updated accordingly.

> [!IMPORTANT]
> In order to use this, you need to update both the `l10n_es`, `l10n_es_reports` modules and install the new `l10n_es_reports_2024` module.

[Orden HAC/819/2024]: https://www.boe.es/eli/es/o/2024/07/30/hac819
[Real Decreto-ley 4/2024]: https://www.boe.es/buscar/act.php?id=BOE-A-2024-12944

[task-4147046](https://www.odoo.com/odoo/all-tasks/4147046)

Related to https://github.com/odoo/odoo/pull/179797

Forward-Port-Of: odoo/enterprise#71005
Forward-Port-Of: odoo/enterprise#69736

Forward-Port-Of: odoo/enterprise#71014

Forward-Port-Of: odoo/enterprise#71014