Steps to reproduce: 1. Install `l10n_in_ewaybill_stock` and `sale_management` 2. Activate Units of measure 3. Create SO and add SO line with a product uom having units 4. Set this parameter `Quantity -> 1`, `UoM -> Dozen`, `Price Unit -> 12` 5. Confirm SO and related picking delivery 6. Create and generate E-waybill 7. Print Receipt The actual Taxable amount should be Rs. 12 but instead it shows 144 In this commit we fix the following issue opw-4728253 --- I confirm I hav

Steps to reproduce:
1. Install `l10n_in_ewaybill_stock` and `sale_management`
2. Activate Units of measure
3. Create SO and add SO line with a product uom having units
4. Set this parameter `Quantity -> 1`, `UoM -> Dozen`, `Price Unit -> 12`
5. Confirm SO and related picking delivery
6. Create and generate E-waybill
7. Print Receipt

The actual Taxable amount should be Rs. 12 but instead it shows 144

In this commit we fix the following issue

opw-4728253



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

Forward-Port-Of: odoo/odoo#206285
Forward-Port-Of: odoo/odoo#206094

Before this commit, several invisible fields were present in the views in `l10n_ch`, whereas after https://github.com/odoo/odoo/pull/162009 these fields need to be either justified or removed. The needed fields are fetched automatically after https://github.com/odoo/odoo/pull/137031. This commit adds a comment to each field so that the tests pass in stable versions, to avoid potential issues with inheritance in custom views. We will removes the unnecessary invisible fields in master.

Before this commit, several invisible fields were present in the views in `l10n_ch`, whereas after https://github.com/odoo/odoo/pull/162009 these fields need to be either justified or removed.

The needed fields are fetched automatically after https://github.com/odoo/odoo/pull/137031.

This commit adds a comment to each field so that the tests pass in stable versions, to avoid potential issues with inheritance in custom views.

We will removes the unnecessary invisible fields in master.

opw-4629332




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

Forward-Port-Of: odoo/odoo#205501

Before this commit, cash payments from cancelled orders were included in the total cash payments, leading to inaccurate bank statements and an incorrect ending balance after closing the session. This issue was not visible during the session closing process, as cancelled orders are correctly excluded from the closing cash control computation. opw-4654848 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#205977 Forward-Po

Before this commit, cash payments from cancelled orders were included in the total cash payments, leading to inaccurate bank statements and an incorrect ending balance after closing the session.

This issue was not visible during the session closing process, as cancelled orders are correctly excluded from the closing cash control computation.

opw-4654848

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

Forward-Port-Of: odoo/odoo#205977
Forward-Port-Of: odoo/odoo#203732

Description of the issue/feature this PR addresses: modified labels are not sent to the ETA Current behavior before PR: -> change an invoice line label -> post the invoice -> send to ETA -> only product name is sent to the ETA Desired behavior after PR is merged: -> change an invoice line label -> post the invoice -> send to ETA -> line label is sent to the ETA this is based on this pr: https://github.com/odoo/odoo/pull/200907 --- I confirm I have signed the CLA and read the PR

Description of the issue/feature this PR addresses:
modified labels are not sent to the ETA
Current behavior before PR:
-> change an invoice line label
-> post the invoice
-> send to ETA
-> only product name is sent to the ETA
Desired behavior after PR is merged:
-> change an invoice line label
-> post the invoice
-> send to ETA
-> line label is sent to the ETA

this is based on this pr: https://github.com/odoo/odoo/pull/200907

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

Forward-Port-Of: odoo/odoo#203793
Forward-Port-Of: odoo/odoo#203275

Printing the E-Way Bill failed if the company logo was not configured, as the QWeb template attempted to render an image using a non-existent logo. Steps to reproduce: - Remove the company logo from the company settings - Try to print an E-Way Bill for any invoice Expected: - The E-Way Bill should be printed successfully without a logo Actual: - PDF generation fails due to a template rendering error Now: - The template checks for the presence of a logo before rendering it, allow

Printing the E-Way Bill failed if the company logo was not configured, as the QWeb template attempted to render an image using a non-existent logo.

Steps to reproduce:
- Remove the company logo from the company settings
- Try to print an E-Way Bill for any invoice

Expected:
- The E-Way Bill should be printed successfully without a logo

Actual:
- PDF generation fails due to a template rendering error

Now:
- The template checks for the presence of a logo before rendering it, allowing the E-Way Bill to print even if the logo is not set.


opw-4709233


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

Forward-Port-Of: odoo/odoo#206320
Forward-Port-Of: odoo/odoo#206190

After this commit, when a company is selected, the order is set to "to_invoice = true" by default. The user is still able to put it back to false if he wants. task-id: 4658640 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#202736 Forward-Port-Of: odoo/odoo#202515

After this commit, when a company is selected, the order is set to "to_invoice = true" by default. The user is still able to put it back to false if he wants.

task-id: 4658640

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

Forward-Port-Of: odoo/odoo#202736
Forward-Port-Of: odoo/odoo#202515

Before this commit, deleting a synced orderline linked to an event registration and then adding a new event product to the same order could cause an error when validating the order. Steps to reproduce: 1. Enable Events with PoS 2. Enable Online Payment 3. Add a ticket product to the order 4. Proceed to the payment screen, and select online payment 4. Delete the ticket line and add a different one 5. Complete the order using cash or another offline payment method opw-4714193 --- I

Before this commit, deleting a synced orderline linked to an event registration and then adding a new event product to the same order could cause an error when validating the order.

Steps to reproduce:
1. Enable Events with PoS
2. Enable Online Payment
3. Add a ticket product to the order
4. Proceed to the payment screen, and select online payment
4. Delete the ticket line and add a different one
5. Complete the order using cash or another offline payment method

opw-4714193

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

Forward-Port-Of: odoo/odoo#205418

Replace the non-standard '🠖' (->) character with an arrow icon in the `_search_render_results()` method for consistent and proper rendering across browsers and platforms. Forward-Port-Of: odoo/odoo#205862

Replace the non-standard '🠖' (->) character with an arrow icon in the
`_search_render_results()` method for consistent and proper rendering
across browsers and platforms.

Forward-Port-Of: odoo/odoo#205862

# Context: A recent improvement (https://github.com/odoo/odoo/pull/203739) slightly changed how the search domain for `ancestors` operates. Before it ignored note subtypes, i.e. `'subtype_id', '!=', note_type.id`. After the PR, it now matches all messages as long as they have a subtype. In doing so, it didn't account for the fact that in some production database, you might have `mail.message` records that have **no** message_id set, i.e. `message_id == False`. In such cases a traceba

# Context:

A recent improvement (https://github.com/odoo/odoo/pull/203739) slightly changed how the search domain for `ancestors` operates. Before it ignored note subtypes, i.e. `'subtype_id', '!=', note_type.id`.

After the PR, it now matches all messages as long as they have a subtype.

In doing so, it didn't account for the fact that in some production database, you might have `mail.message` records that have **no** message_id set, i.e. `message_id == False`.

In such cases a traceback would be generated when sending a message from a mail.thread having an ancestor without `message_id` set.

Example:
```
    references = ' '.join(m.message_id for m in (ancestors + message_sudo))
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: sequence item 1: expected str instance, bool found
```

While such records *should* not exist when using the ORM, they might be the result of:
* certain upgrade scripts that use direct SQL (cf https://github.com/odoo/upgrade/blob/06b9e7f3cd98c383698695d6028bb7adefb6f805/migrations/base_vat/saas~16.3.1.0/pre-migrate.py#L104-L120)
* direct SQL inserts by users or/and customisations

# Proposed solution:
Since there are no ad-hoc mecanismes to fix such records on productions, the next best thing would be to simply adapt the search domain for `ancestors` and ignore any records where `message_id == False`. Indeed, if there is no `message_id` it makes no sense to try to add it in the references header.

# Reproduction steps:
1) Setup database and install contacts
2) Pick a contact and post a log note
3) For this new `mail.message` write `message_id == False` in the backend 4) Try to send a new message to the contact
-> Traceback

OPW-4728399


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

Forward-Port-Of: odoo/odoo#206279

Purpose of this commit: This commit aims to restrict the log notes to not be squashed when posted on a record from a chat window. task-4718225 Forward-Port-Of: odoo/odoo#206114 Forward-Port-Of: odoo/odoo#205998

Purpose of this commit:
This commit aims to restrict the log notes to not be squashed 
when posted on a record from a chat window.

task-4718225

Forward-Port-Of: odoo/odoo#206114
Forward-Port-Of: odoo/odoo#205998

Forward-Port-Of: odoo/odoo#206289

Forward-Port-Of: odoo/odoo#206289

… behavior Fix the demo mode of Peppol to be closer to the behavior in production. task-no (review with TSB/PMAX 31/03/25) Forward-Port-Of: odoo/odoo#206265 Forward-Port-Of: odoo/odoo#204241

… behavior

Fix the demo mode of Peppol to be closer to the behavior in production.

task-no (review with TSB/PMAX 31/03/25)

Forward-Port-Of: odoo/odoo#206265
Forward-Port-Of: odoo/odoo#204241

Revealed by the nightly single app tests now testing every module, possibly some other module (and formerly demo data) hides the issue by setting a country which happens to work on the current company. Since #127204 `action_stripe_connect_account` will raise an error if the current company's country is not in `SUPPORTED_COUNTRIES`. When installing the module and running the test, the country is `False`, which is not a country supported by stripe. Ensure a supported country is set before ru

Revealed by the nightly single app tests now testing every module, possibly some other module (and formerly demo data) hides the issue by setting a country which happens to work on the current company.

Since #127204 `action_stripe_connect_account` will raise an error if the current company's country is not in `SUPPORTED_COUNTRIES`. When installing the module and running the test, the country is `False`, which is not a country supported by stripe.

Ensure a supported country is set before running the test.

https://runbot.odoo.com/odoo/error/163118

Forward-Port-Of: odoo/odoo#206141
Forward-Port-Of: odoo/odoo#206066

`payment` does not depend on `account`, it thus can't unconditionally use `account` groups. Skip tests if `account` is not installed (matches `account_custom` behaviour). `account_custom` does not depend on `product`, so can't use `product.product` unconditionally. `setUpClass` doesn't seem useful so just remove it entirely. Forward-Port-Of: odoo/odoo#206196

`payment` does not depend on `account`, it thus can't unconditionally use `account` groups. Skip tests if `account` is not installed (matches `account_custom` behaviour).

`account_custom` does not depend on `product`, so can't use `product.product` unconditionally. `setUpClass` doesn't seem useful so just remove it entirely.

Forward-Port-Of: odoo/odoo#206196

In the calendar application, when clicking on an event, a window opens. In this window, we can select “yes,” “no,” or “maybe.” When one of the buttons is selected and the mouse hovers over the button to its right, the border of the selected button disappears. This commit fixes this display issue to ensure that all four borders remain visible when hovering over the button adjacent to the selected one. Current behavior before PR: <img width="430" alt="Screenshot 2025-03-31 at 18 14 31" src="ht

In the calendar application, when clicking on an event, a window opens. In this window, we can select “yes,” “no,” or “maybe.” When one of the buttons is selected and the mouse hovers over the button to its right, the border of the selected button disappears. This commit fixes this display issue to ensure that all four borders remain visible when hovering over the button adjacent to the selected one.

Current behavior before PR:
<img width="430" alt="Screenshot 2025-03-31 at 18 14 31" src="https://github.com/user-attachments/assets/803358b7-139d-44d3-a5b2-d381bd2fc998" />

<img width="434" alt="Screenshot 2025-03-31 at 18 14 35" src="https://github.com/user-attachments/assets/4a2ce979-1da5-4c19-8e82-0bfe651e9c27" />


Desired behavior after PR is merged:
<img width="430" alt="Screenshot 2025-03-31 at 18 13 11" src="https://github.com/user-attachments/assets/c9faf40d-e913-481a-ac57-fc341091d56b" />
<img width="436" alt="Screenshot 2025-03-31 at 18 13 06" src="https://github.com/user-attachments/assets/12c0745f-a02a-4e59-99f3-4d6a2c791162" />

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

Forward-Port-Of: odoo/odoo#204197

Currently, an error occurs when a user tries to duplicate more than one payment term at once from the list view. **Steps to produce:** - Install the `account` module. - Navigate to `Invoicing > Payment Terms` (list view). - Select at least two records and duplicate them. - Observe the error. `ValueError - Expected singleton: account.payment.term(3, 4, 5, 6, 7, 8, 9, 10)` An error occurs because the **copy** method accesses `self.name`, assuming a single record, when multiple records

Currently, an error occurs when a user tries to duplicate more than one payment term at once from the list view.

**Steps to produce:**
- Install the `account` module.
- Navigate to `Invoicing > Payment Terms` (list view).
- Select at least two records and duplicate them.
- Observe the error.

`ValueError - Expected singleton: account.payment.term(3, 4, 5, 6, 7, 8, 9, 10)`

An error occurs because the **copy** method accesses `self.name`, assuming a single record, when multiple records are duplicated, causing the `ValueError`.

[1] - https://github.com/odoo/odoo/blob/6b970a0bfbcdac92d05389aac994c0db36730a34/addons/account/models/account_payment_term.py#L270

This commit ensures that each duplicated payment term has its name individually updated after being copied.

Sentry - 6531350963

Forward-Port-Of: odoo/odoo#205650

Purpose ======= Odoo 18.1 introduced a new unit of measure: "Milliliter (ml)" in the uom.uom model. This commit adds `l10n_in_code` for this unit in l10n_in: - "Milliliter (ml)" with code "MLT-MILILITRE" (https://einvoice1.gst.gov.in/Others/MasterCodes) (select UQC Codes) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#204732

Purpose
=======
Odoo 18.1 introduced a new unit of measure: "Milliliter (ml)"
in the uom.uom model.

This commit adds `l10n_in_code` for this unit in l10n_in:
- "Milliliter (ml)" with code "MLT-MILILITRE"

(https://einvoice1.gst.gov.in/Others/MasterCodes) (select UQC Codes)

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

Forward-Port-Of: odoo/odoo#204732

Steps to reproduce: - Install `project` - Create a new `project` and `tasks` within it. - Share the project with the portal user with edit access mode. Issue: - The color picker is not accessible through the portal. Fix: - Hide the color picker for portal users when editing color in shared tasks. task-4495861 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#206253 Forward-Port-Of: odoo/odoo#2020

Steps to reproduce:

- Install `project`
- Create a new `project` and `tasks` within it.
- Share the project with the portal user with edit access mode.

Issue:

- The color picker is not accessible through the portal.

Fix:

- Hide the color picker for portal users when editing color in shared tasks.

task-4495861






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

Forward-Port-Of: odoo/odoo#206253
Forward-Port-Of: odoo/odoo#202058

Currently, a traceback occurs when the user tries to cancel the Manufacturing Order which is linked with a Purchase Order ### Steps to reproduce: 1) Install purchase and MRP 2) Enable UOm and multi-step routes from settings 3) Unarchive the MTO route 4) Create 2 products: - FP: route Manufacturing, MTO - COMP: Route buy, MTO and a set vendor 5) Create a BOM with FP as Final Product and COMP as component. 6) Create and confirm an MO for 1 unit of FP 7) Cancel the MO #### > Qweb

Currently, a traceback occurs when the user  tries to cancel the Manufacturing Order which is linked with a Purchase Order

### Steps to reproduce:

1) Install purchase and MRP
2) Enable UOm and multi-step routes from settings
3) Unarchive the MTO route
4) Create 2 products:
	- FP: route Manufacturing, MTO
	- COMP: Route buy, MTO and a set vendor
5) Create a BOM with FP as Final Product and COMP as component.
6) Create and confirm an MO for 1 unit of FP
7) Cancel the MO
#### > Qweb Error: 'purchase.order.line' object has no attribute 'product_uom' > The MO was not cancelled

### Cause of the issue:

In order_exceptions we do get objects like `sale.order.line`, `purchase.order.line`, `stock.move`etc.... 
depending on the MRP order.

Which is used in the `mrp.exception_on_mo` template to display the The UOM, product name, etc., 
in the activity can be found in the line below. 

https://github.com/odoo/odoo/blob/51c6a0dd06a362d5f8327741287beb422f250b7d/addons/mrp/data/mail_templates.xml#L18

But when we get `purchase.order.line` in `order_exception`,we get the 
above traceback because product_uom is changed to `product_uom_id` from the below commit.

https://github.com/odoo/odoo/pull/186250/files#diff-5684edced9bdfc98021a85de4c6cdf691ea7add74e56ab50334a1d7db9ef4224L32-R33

We can resolve this issue by checking whether the product_uom_id available in the move_raw_id or not.

sentry-6240577568

Forward-Port-Of: odoo/odoo#202497

This PR introduces a regression test to ensure that the sitemap remains in the default language of the website, regardless of the language version being accessed. Tests 2 scenarios: - First, configure a website with English and French language. - Set the default language to French. - Access the sitemap at /sitemap.xml -> The sitemap should be displayed in French. - Second, let the default language to be English. - Navigate to the French version of the website at /fr. - Access t

This PR introduces a regression test to ensure that the sitemap
remains in the default language of the website, regardless of the
language version being accessed.

Tests 2 scenarios:

- First, configure a website with English and French language.
- Set the default language to French.
- Access the sitemap at /sitemap.xml -> The sitemap should be displayed
    in French.
- Second, let the default language to be English.
- Navigate to the French version of the website at /fr.
- Access the sitemap at /sitemap.xml -> The sitemap should now be
    displayed in English.

This test addresses an issue that was previously fixed in commit
https://github.com/odoo/odoo/commit/809854c5d10735fb280141f5291bdb84d8d36569, but lacked a corresponding test to prevent future
regressions. This test ensures the bug reported in task-3935135 does ``
not reoccur.

**Added test in website_blog as it has routes that were translated.
Reference:
[1]: https://github.com/odoo/odoo/pull/154993#pullrequestreview-1900639267

Forward-Port-Of: odoo/odoo#190779

to reproduce: ============= - with employee having attendace houre based contract - set in attendace settigns that overtime should be approved by manager - create attendace for this employee with overtime pending for approval - create payslip for this employee -> the overtime is included in the payslip even if it is not approved Problem: ======== unapproved overtimes are not filtred while computing payslip lines Solution: ========= - add a filter to exclude unapproved overtimes

to reproduce:
=============
- with employee having attendace houre based contract
- set in attendace settigns that overtime should be approved by manager
- create attendace for this employee with overtime pending for approval
- create payslip for this employee

-> the overtime is included in the payslip even if it is not approved

Problem:
========
unapproved overtimes are not filtred while computing payslip lines

Solution:
=========
- add a filter to exclude unapproved overtimes in payslip line computation

opw-4610454

Forward-Port-Of: odoo/enterprise#83449

Revert odoo/enterprise#81587 because errors are triggered on dry-run. Also see discussion here: ref: https://github.com/odoo/enterprise/pull/82900#issuecomment-2800848343 Forward-Port-Of: odoo/enterprise#83422 Forward-Port-Of: odoo/enterprise#83391

Revert odoo/enterprise#81587 because errors are triggered on dry-run.

Also see discussion here:
ref: https://github.com/odoo/enterprise/pull/82900#issuecomment-2800848343

Forward-Port-Of: odoo/enterprise#83422
Forward-Port-Of: odoo/enterprise#83391

…mesheet **Issue** In a subscription, the qty delivered of a SOL with "Prepaid" invoicing policy wasn't updated when timesheets were added. **Steps to reproduce** 1. Have a service subscription product with an invoicing policy "Prepaid/Fixed price" and creating a task on order. 2. Create a monthly subscription with a start date 15 days in the past 3. Add some timesheet hours on the task. 4. Run the "Subscription: generate recurring invoices" cron. - Actual: quantity delivered on th

…mesheet

**Issue**
In a subscription, the qty delivered of a SOL with "Prepaid" invoicing policy
wasn't updated when timesheets were added.

**Steps to reproduce**
1. Have a service subscription product with an invoicing policy "Prepaid/Fixed
price" and creating a task on order.
2. Create a monthly subscription with a start date 15 days in the past
3. Add some timesheet hours on the task.
4. Run the "Subscription: generate recurring invoices" cron.
- Actual: quantity delivered on the SOL stays at 0.
- Expected: timesheet hours falling during the subscription period are added
to the delivered quantity of the line.

**Cause**
Commit https://github.com/odoo/enterprise/commit/a6420bdacab3b9c9f440f48db3b442e6b6c7b655 added a new module overwriting
the computation of the delivered quantitiy for recurring lines based on
timesheets, for products with an invoicing policy `delivered_timesheet`.
However, the computation is overriden for all timesheet lines selected by
https://github.com/odoo/enterprise/blob/a6420bdacab3b9c9f440f48db3b442e6b6c7b655/sale_subscription_timesheet/models/sale_order_line.py#L11-L12

A second filtering is applied later
https://github.com/odoo/enterprise/blob/a6420bdacab3b9c9f440f48db3b442e6b6c7b655/sale_subscription_timesheet/models/sale_order_line.py#L21
Which exluces products with an invoicing policy different than
`delivered_timesheet`

**Solution**
For products with a "prepaid" invoicing policy, compute the delivered
quantities the same way: the timesheets delivered during the subscription
period.
Note that as explained in a comment, `Side effect: It won't work for the
first period if the invoice cron never run. (the next invoice date has never
been incremented)`

opw-4509495

Forward-Port-Of: odoo/enterprise#82917
Forward-Port-Of: odoo/enterprise#82806

Currently, an error may occur when we try to export the trial balance with the SAT (XML) format. This is because a None id is used to browse the account, due to a more specific account_group. Steps to reproduce: - Install l10n_mx_reports. - Create an account_group with a more specific account, such as 401.01.01 - The 4, 401, and 401.01 groups are created with demo data. - Go to trial balance and try exporting with "SAT (XML)". An error will occur (`AttributeError: 'bool' object has

Currently, an error may occur when we try to export the trial balance with the SAT (XML) format. This is because a None id is used to browse the account, due to a more specific account_group.

Steps to reproduce:
- Install l10n_mx_reports.
- Create an account_group with a more specific account, such as 401.01.01
    - The 4, 401, and 401.01 groups are created with demo data.
- Go to trial balance and try exporting with "SAT (XML)".

An error will occur (`AttributeError: 'bool' object has no attribute 'startswith'`) because the account is None, so account have no type.

opw-4716047

Forward-Port-Of: odoo/enterprise#83407
Forward-Port-Of: odoo/enterprise#83197

Steps to reproduce: 1. Create a new BoM w/ a pass/fail operation step 2. Create a manufacturing order using that BoM 3. Go the the Quality app 4. Open the quality check created for the MO 5. Click on Pass (or Fail, does not matter) 6. Go back to the MO and click Produce All 7. The qty_passed/qty_failed is not computed on the quality check opw-4552103 Forward-Port-Of: odoo/enterprise#80291

Steps to reproduce:
1. Create a new BoM w/ a pass/fail operation step
2. Create a manufacturing order using that BoM
3. Go the the Quality app
4. Open the quality check created for the MO
5. Click on Pass (or Fail, does not matter)
6. Go back to the MO and click Produce All
7. The qty_passed/qty_failed is not computed on the quality check

opw-4552103

Forward-Port-Of: odoo/enterprise#80291

The SP-API doesn't support SKU containing commas, not even when escaping and listing them in a correct CSV like string, as they'll be considered as either separate SKU or a different one, thus leading to an error saying there are too many identifiers, or not recognizing them anyway. In order to let the synchronization continue for the other items, ensure their SKU are valid beforehand. As from Amazon side, using a comma is a valid value, we can't constrain the SKU either. opw-4710435

The SP-API doesn't support SKU containing commas, not even when escaping
and listing them in a correct CSV like string, as they'll be considered
as either separate SKU or a different one, thus leading to an error
saying there are too many identifiers, or not recognizing them anyway.
In order to let the synchronization continue for the other items, ensure
their SKU are valid beforehand.

As from Amazon side, using a comma is a valid value, we can't constrain
the SKU either.

opw-4710435

Forward-Port-Of: odoo/enterprise#83367

STEPS ------------ 0. You'll require IAP credit for PDF extraction 1. Create 1 POs (we'll call it PO-1) and set the vendor as the current company 2. Duplicate PO-1 (we'll call the duplicate PO-2) and change the amount value of one product 3. Create an invoice with the extact same values as PO-2 and set the customer reference (in the 'Other Info' tab) to "PO-2"; we'll call it INV-1 4. Create a bill and use the Auto-Complete field to manually select PO-1 5. Drag and drop INV-1 in the chatte

STEPS
------------
0. You'll require IAP credit for PDF extraction
1. Create 1 POs (we'll call it PO-1) and set the vendor as the current company
2. Duplicate PO-1 (we'll call the duplicate PO-2) and change the amount value of one product
3. Create an invoice with the extact same values as PO-2 and set the customer reference (in the 'Other Info' tab) to "PO-2"; we'll call it INV-1
4. Create a bill and use the Auto-Complete field to manually select PO-1
5. Drag and drop INV-1 in the chatter -> IAP should trigger -> The chatter says
'''
The invoice already contains lines, it was not updated from the attachment.

'''
but yet, it updated the purchase reference to PO-2 and updated the lines

OBJECTIVE
------------
If a bill has lines, it should not be updated with the content of the PO.

task-4633298

Forward-Port-Of: odoo/enterprise#83336
Forward-Port-Of: odoo/enterprise#83246

**Steps to reproduce:** - Install Accounting and l10n_pe_edi - Switch to a Peruvian company (e.g. PE Company) - Configure Peruvian localization (https://www.odoo.com/documentation/17.0/applications/finance/fiscal_localizations/peru.html) - Create an invoice: * Customer: Comercial Constructora los Patitos S.A. * Operation Type: [0101] Internal sale * Invoice Lines: - Product: [any with a UNSPSC Category] - Taxes: 18% - Terms and Conditions: [text containing special cha

**Steps to reproduce:**
- Install Accounting and l10n_pe_edi
- Switch to a Peruvian company (e.g. PE Company)
- Configure Peruvian localization (https://www.odoo.com/documentation/17.0/applications/finance/fiscal_localizations/peru.html)
- Create an invoice:
  * Customer: Comercial Constructora los Patitos S.A.
  * Operation Type: [0101] Internal sale
  * Invoice Lines:
    - Product: [any with a UNSPSC Category]
    - Taxes: 18%
    - Terms and Conditions: [text containing special characters like '/' or '.']
- Confirm the invoice
- Process UBL 2.1

**Issue:**
In the XML, the content of <cbc:Note> has been stripped of all special characters like [/\!?+-=%.,;:()].
Only "whitespace" special characters should be excluded (i.e. '\n', '\u00A0',...).

opw-4659655

Forward-Port-Of: odoo/enterprise#82787

### Steps to reproduce: - In the settings enable by products. - Create two products FP and SN where SN is tracked by serial numbers - Create and confirm an MO for FP where SN is a by product - Open the shopfloor > Register By-Product > generate serial numbers > input SN0012 > Generate > Save #### > your input was not taken into account, not lot was created. ### Cause of the issue: Clicking on `Register By-Product` and generate serial numbers will open the `stock.generate_serial_d

### Steps to reproduce:

- In the settings enable by products.
- Create two products FP and SN where SN is tracked by serial numbers
- Create and confirm an MO for FP where SN is a by product
- Open the shopfloor > Register By-Product > generate serial numbers
  > input SN0012 > Generate > Save
#### > your input was not taken into account, not lot was created.

### Cause of the issue:

Clicking on `Register By-Product` and generate serial numbers will open the `stock.generate_serial_dialog`. Clicking on Generate will then call the `_onGenerate` method and an rpc call of the
`action_generate_lot_line_vals` will be made:
https://github.com/odoo/odoo/blob/a0542b13f679d4dc20d61eb62e4eb5106d6abe5a/addons/stock/static/src/widgets/lots_dialog.xml#L12 https://github.com/odoo/odoo/blob/a0542b13f679d4dc20d61eb62e4eb5106d6abe5a/addons/stock/static/src/widgets/generate_serial.js#L34 However, if you triggered these actions from the shopfloor, you never provided a `default_picking_type_id` in the context so that the lot will never be created by any mean:
https://github.com/odoo/odoo/blob/a0542b13f679d4dc20d61eb62e4eb5106d6abe5a/addons/stock/models/stock_move.py#L919-L927 https://github.com/odoo/odoo/blob/a0542b13f679d4dc20d61eb62e4eb5106d6abe5a/addons/stock/models/stock_move.py#L945-L948

opw-4544734

Forward-Port-Of: odoo/enterprise#83356
Forward-Port-Of: odoo/enterprise#82355

Steps to reproduce: ------------------- * Install l10n_cl_edi_stock * Create a new Transfer * Add as customer a Contact that is part of a Company * Print Delivery Guide SII DTE 52 (CL) > Observation: Why the fix: ------------ The name of the company has to be shown not the actual name of ths customer Legal requirement in Chile ref: https://www.sii.cl/factura_electronica/formato_dte.pdf https://github.com/odoo/odoo/pull/172793 opw-4676871 Forward-Port-Of: odoo/enterprise#83311

Steps to reproduce:
-------------------
* Install l10n_cl_edi_stock
* Create a new Transfer
* Add as customer a Contact that is part of a Company
* Print Delivery Guide SII DTE 52 (CL)
> Observation:

Why the fix:
------------
The name of the company has to be shown not the actual name of ths customer Legal requirement in Chile
ref: https://www.sii.cl/factura_electronica/formato_dte.pdf https://github.com/odoo/odoo/pull/172793

opw-4676871

Forward-Port-Of: odoo/enterprise#83311

Steps to Reproduce: - Open the Industry FSM app and navigate to the Activity view. - Click on any task to open its form view. Issue: - A traceback error occurs when opening a task on large screens due to 'newWindow' being undefined. Solution: - Passed the 'options' argument to super.openRecord in FsmMyTaskActivityController to ensure 'newWindow' is defined on large screens. - Ensured consistent behavior for openRecord across devices. task-4664793 Forward-Port-Of: odoo/enterprise

Steps to Reproduce:
-  Open the Industry FSM app and navigate to the Activity view.
-  Click on any task to open its form view.

Issue:
- A traceback error occurs when opening a task on large screens due to 'newWindow' being undefined.

Solution:
- Passed the 'options' argument to super.openRecord in FsmMyTaskActivityController to ensure 'newWindow' is defined on large screens.
- Ensured consistent behavior for openRecord across devices.

task-4664793

Forward-Port-Of: odoo/enterprise#82646