### Issue: - When picking up a SO in POS, the discount on products sold with a non groupable UOM disappears. ### Steps to reproduce: - Create a SO in the sales app. - Include a product that has a UOM of which the uom category is not grouped in POS (g for example). - Add a discount to the product. - Pick up the order in POS. - Notice that the discount is not applied. ### Solution: - In `_onClickSaleOrder` I set the discount on the `splitted_line` before adding it to the orderline.

### Issue:
- When picking up a SO in POS, the discount on products sold with a non groupable UOM disappears.

### Steps to reproduce:
- Create a SO in the sales app.
- Include a product that has a UOM of which the uom category is not grouped in POS (g for example).
- Add a discount to the product.
- Pick up the order in POS.
- Notice that the discount is not applied.

### Solution:
 - In `_onClickSaleOrder` I set the discount on the `splitted_line` before adding it to the orderline.

opw-4133659

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

Forward-Port-Of: odoo/odoo#187441
Forward-Port-Of: odoo/odoo#185109

The dropdown selection for tracking/lot number is misaligned when the users has a rtl language. Steps to reproduce: ------------------- * Switch the current user to a rtl language (arabic for ex) * Open shop session * Select the drawer product > Observation: dropdown selection is misaligned Before vs after fix: ------------------------- RTL computer: * Before:  * After: ![r

The dropdown selection for tracking/lot number is misaligned when the users has a rtl language.

Steps to reproduce:
-------------------
* Switch the current user to a rtl language (arabic for ex)
* Open shop session
* Select the drawer product
> Observation: dropdown selection is misaligned

Before vs after fix:
-------------------------
RTL computer:
* Before:
  ![rtl_before_computer](https://github.com/user-attachments/assets/49036d2f-3612-49ca-b21f-85751873ebd6)
* After:
  ![rtl_after_computer](https://github.com/user-attachments/assets/fe4d2d36-0020-48d0-b2dd-c2a29cfd4c27)
  
RTL mobile:
* Before:
  ![rtl_before_mobile](https://github.com/user-attachments/assets/fd97e60a-437a-4b3d-85b3-b7db04590fcc)
 * After:
   ![rtl_after_mobile](https://github.com/user-attachments/assets/a5c8abd8-b80d-4292-8123-1ebeccfc8776)
 
LTR computer:
* Before:
  ![ltr_before_computer](https://github.com/user-attachments/assets/8c6ce80c-992c-4d4f-aca2-7df7939da868)
* After:
  ![ltr_after_computer](https://github.com/user-attachments/assets/d4ae6f1b-4ec8-457d-b5e7-08f32044e45c)
  
LTR mobile
* Before:
  ![ltr_before_mobile](https://github.com/user-attachments/assets/81c5c093-13df-4a4c-9865-61c45bc9064d)
* After:
  ![ltr_after_mobile](https://github.com/user-attachments/assets/736d9975-099b-4622-be9a-9d619367f750)
  
Also works if we move the popup around.

opw-4187095

Forward-Port-Of: odoo/odoo#185878

Before this PR, query strings were added to the attachment of URL types. This is incorrect since those URLs can already have query strings, and the added query strings don't make sense for non-binary attachments. Forward-Port-Of: odoo/odoo#187580 Forward-Port-Of: odoo/odoo#187522

Before this PR, query strings were added to the attachment of URL types. This is incorrect since those URLs can already have query strings, and the added query strings don't make sense for non-binary attachments.

Forward-Port-Of: odoo/odoo#187580
Forward-Port-Of: odoo/odoo#187522

Steps to reproduce: - Project app > Any project > ':' Menu > Burndown Chart - Add any custom filter > Click Add - Sticky Note 'Domain is invalid. Please corect it' The burndown chart view is dependent on groupby argument 'date', if you try to remove the groupby block from the search bar an error message will appear to stop you. This works properly when passing through `web_read_group` but here we take a slightly different path. When adding a custom domain to the search bar, we validate

Steps to reproduce:
- Project app > Any project > ':' Menu > Burndown Chart
- Add any custom filter > Click Add
- Sticky Note 'Domain is invalid. Please corect it'

The burndown chart view is dependent on groupby argument 'date', if you try to remove the groupby block from the search bar an error message will appear to stop you. This works properly when passing through `web_read_group` but here we take a slightly different path.

When adding a custom domain to the search bar, we validate that domain by simulating an SQL query using said domain. This request is made independantly of `web_read_group` since it's not intended to be displayed, hence why we don't have the groupby argument.

This causes the query building process to fail, so a default value is needed to restore the flow. Since we only want to validate the domain it does not matter what we put in so I used the default search value.

opw-4300254

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

Forward-Port-Of: odoo/odoo#186402

We have to await for `_initiatePaymentFlow()` completion to ensure we correctly got the result of the transaction route. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187618 Forward-Port-Of: odoo/odoo#187527

We have to await for `_initiatePaymentFlow()` completion to ensure we correctly got the result of the transaction route.

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

Forward-Port-Of: odoo/odoo#187618
Forward-Port-Of: odoo/odoo#187527

Step to reproduce. 1. Drag and drop a Contact Us Form 2. Select the form action as : " Apply for Job" 3. Select a field Type : "Activities" or "Kanban Stage" 4. Now on other field set visibility depending on this field 5. Now set the visibility options. -> Visibility value shows ID instead actual value/name. Prior to this commit, fields with conditional visibility showed the record's ID instead of its display name when the dependent field was a checkbox or radio button. This commit

Step to reproduce.
1. Drag and drop a Contact Us Form
2. Select the form action as : " Apply for Job"
3. Select a field Type : "Activities" or "Kanban Stage"
4. Now on other field set visibility depending on this field
5. Now set the visibility options.
-> Visibility value shows ID instead actual value/name.

Prior to this commit, fields with conditional visibility showed the
record's ID instead of its display name when the dependent field was a
checkbox or radio button.

This commit fix the issue by displaying the displayName of the record
instead ID.

task-4267217

Forward-Port-Of: odoo/odoo#187030
Forward-Port-Of: odoo/odoo#184232

Problem: If the product image size is smaller than `$o-form-picture-size` or is an SVG without intrinsic size, it uses the original image size or displays as 0px in the case of SVGs without intrinsic size. The desired behavior is for the image to always display at `$o-form-picture-size`. Steps to reproduce: - Add a small or SVG image without intrinsic size to a product. - The image will not display correctly. opw-4119433 --- I confirm I have signed the CLA and read the PR guidelin

Problem:
If the product image size is smaller than `$o-form-picture-size` or is an SVG without intrinsic size, it uses the original image size or displays as 0px in the case of SVGs without intrinsic size. The desired behavior is for the image to always display at `$o-form-picture-size`.

Steps to reproduce:

- Add a small or SVG image without intrinsic size to a product.
- The image will not display correctly.

opw-4119433

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

Forward-Port-Of: odoo/odoo#178526

Currently, an exception was generated when the user tries to open their account details in the portal (url: my/account) error: `KeyError: 'partner_sudo'` This error was generated because when the user tries to open their account detail in the portal, we do not have 'partner_sudo'. Recentley refacto code with https://github.com/odoo/odoo/commit/453cfab758505ae15135703fb7be8bdb54981444 replaced `partner` with `partner_sudo` for the getting partner in the website sale address (`shop/addres

Currently, an exception was generated when the user tries to open their account details in the portal (url: my/account)

error: `KeyError: 'partner_sudo'`

This error was generated because when the user tries to open their account detail in the portal, we do not have 'partner_sudo'.

Recentley refacto code with https://github.com/odoo/odoo/commit/453cfab758505ae15135703fb7be8bdb54981444 replaced `partner` with `partner_sudo` for the getting partner in the website sale address (`shop/address`) and we have the new key because the template 'partner_info' called from template 'address' see [1] and `partner_sudo` set from [2] for address. But when we call the 'partner_info' from template 'portal_my_details_fields' at [3], we do not have `partner_sudo`

This commit will fix the above issue by passing `partner_sudo` in the template at the time prepare value for opening account detail in portal.

[1] - https://github.com/odoo/odoo/blob/3ea0c936c01a7c55ee8fa6ee64fd8e89b2a04f5f/addons/l10n_ar_website_sale/views/templates.xml#L60
[2] - https://github.com/odoo/odoo/blob/3ea0c936c01a7c55ee8fa6ee64fd8e89b2a04f5f/addons/website_sale/controllers/main.py#L1119
[3] - https://github.com/odoo/odoo/blob/3ea0c936c01a7c55ee8fa6ee64fd8e89b2a04f5f/addons/l10n_ar_website_sale/views/templates.xml#L68

sentry-5725856236

Forward-Port-Of: odoo/odoo#186872

Previously, the l10n_id_kode_transaksi field was invisible on the invoice form view. This is because the xpath was incorrectly done. This solution is inspired to what is already done in 18.0. Steps to reproduce: - Install l10n_id_efaktur - Select ID company - Create an Indonesian customer with a VAT number, and select boolean field PKP - Create an invoice, select this customer, and add a line with a tax -> the field below Customer has no display name, but the value is visible

Previously, the l10n_id_kode_transaksi field was invisible on the invoice form view.
This is because the xpath was incorrectly done. This solution is inspired to what is already done in 18.0.

Steps to reproduce:
 - Install l10n_id_efaktur
 - Select ID company
 - Create an Indonesian customer with a VAT number, and select boolean field PKP
 - Create an invoice, select this customer, and add a line with a tax

 -> the field below Customer has no display name, but the value is visible

opw-4315901


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

Forward-Port-Of: odoo/odoo#187294

Steps to reproduce: - In Website edit mode. - Drag and drop a "Text" block into the page. - Click on the first paragaph of the "Text" block. - click the "Insert media" button of the text toolbar. - A traceback occurs. The bug was introduced in commit [1], where we checked that "this.props.media" was not undefined before calling the "closest" function on it. However, this was incorrect because, in cases where "this.props.media" was false, the "closest" function was still called, causing

Steps to reproduce:

- In Website edit mode.
- Drag and drop a "Text" block into the page.
- Click on the first paragaph of the "Text" block.
- click the "Insert media" button of the text toolbar.
- A traceback occurs.

The bug was introduced in commit [1], where we checked that "this.props.media" was not undefined before calling the "closest" function on it. However, this was incorrect because, in cases where "this.props.media" was false, the "closest" function was still called, causing the traceback.

With this fix, the "closest" function is not called if "this.props.media" is false.

[1]: https://github.com/odoo/odoo/commit/625c1aa71e17882848dd827f3be6162e49cbc8ca

opw-4335833
opw-4328280
opw-4334279
opw-4328490
opw-4334012
opw-4332500
opw-4332028
opw-4332684
opw-4329687
opw-4331635
opw-4331371
opw-4331287
opw-4332437
opw-4331144
opw-4329646
opw-4328364
opw-4323197
opw-4325959
opw-4322945

Forward-Port-Of: odoo/odoo#187494
Forward-Port-Of: odoo/odoo#187406

Change field calling convention to support dynamic localization and language formatting. Currently, all fields are called with `t-out` instead of `t-field`, making them non-language or locale-sensitive, which results in a uniform format regardless of user preferences. Steps to produce: 1: installed l10n_din5008_sale 2: create a Quotation 3: Send it by email 4: Select DIN5008 in the template selector opw-4189869 Forward-Port-Of: odoo/odoo#181116

Change field calling convention to support dynamic localization and language formatting. Currently, all fields are called with `t-out` instead of `t-field`, making them non-language or locale-sensitive, which results in a uniform format regardless of user preferences.

Steps to produce:
1: installed l10n_din5008_sale
2: create a Quotation
3: Send it by email
4: Select DIN5008 in the template selector


opw-4189869

Forward-Port-Of: odoo/odoo#181116

Steps to reproduce: Install the app l10n_de and switch to a German company Create an invoice Send & Print the Invoice with XRechnung  PDF and XML versions  are stored as attachments in the record (Chatter). Try to delete them form the chatter. When deleting them, the unlink function only removes the link to account.move fields and saves the attachment with a new name: "document detached by user on date". This works fine for the PDF version but not for XML one. This is because `ir_attachmen

Steps to reproduce:
Install the app l10n_de and switch to a German company Create an invoice
Send & Print the Invoice with XRechnung 
PDF and XML versions  are stored as attachments in the record (Chatter). Try to delete them form the chatter. When deleting them, the unlink function only removes the link to account.move fields and saves the attachment with a new name: "document detached by user on date". This works fine for the PDF version but not for XML one.

This is because `ir_attachment.res_field` is set to `ubl_cii_xml_file` for XML version of the attachment, but when filtering to detach them the filter looks for `ir_attachment.res_field` that are set to `ubl_cii_xml_id`.
opw-4273836


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

Forward-Port-Of: odoo/odoo#186603

## Issue: After the changes we have made to sign in 17.0 we stop properly handling the state of the buttons for submit our sign after signing, the problem then is that in Draw mode for example, we are able to submit the sign even before drawing anything, which will allow us to send the document "unsigned", since there will not be any sign. ## Steps to reproduce: 1. Get Sign module. 2. Upload any document to sign. 3. Add sign box and go to sign the document. 4. Now change from Auto to Dr

## Issue: 
After the changes we have made to sign in 17.0 we stop properly handling the state of the buttons for submit our sign after signing, the problem then is that in Draw mode for example, we are able to submit the sign even before drawing anything, which will allow us to send the document "unsigned", since there will not be any sign.

## Steps to reproduce:
1. Get Sign module.
2. Upload any document to sign.
3. Add sign box and go to sign the document.
4. Now change from Auto to Draw.

## Solution: 
We should take into account that it makes sense that everytime we update if our signature is empty, we update the state of the buttons accordingly avoiding this way to be able to sign without an actual sing. The solution address a similar approach at what was already being done with the onChangeName, we move this logic to be handled by a specific function for this buttons 'handleButtonStateChange'.

The fix is part of > [#61981](https://github.com/odoo/enterprise/pull/61981)

opw-3874034

Forward-Port-Of: odoo/odoo#180103
Forward-Port-Of: odoo/odoo#164410

We've added tracking on some fields that are used to compute the cost of cars and also the serial number to know if it has been manually changed. When the value or the cost of the car change, we want to know who modified it and when it has been done. TASK-ID: 4306184 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187032

We've added tracking on some fields that are used to compute the cost of cars and also the serial number to know if it has been manually changed.

When the value or the cost of the car change, we want to know who modified it and when it has been done.

TASK-ID: 4306184




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

Forward-Port-Of: odoo/odoo#187032

Problem: When creating a new e-commerce category, the breadcrumb displays "Unnamed" instead of the actual category name. This happens because the `parents_and_self` field is not recomputed when `parent_path` changes, despite the former depending on the latter. Solution: Ensure that `parents_and_self` is recomputed whenever `parent_path` is updated, so that the correct name is reflected in the breadcrumb. Steps to reproduce: - Open the form to create a new e-commerce category. - After s

Problem:
When creating a new e-commerce category, the breadcrumb displays "Unnamed" instead of the actual category name. This happens because the `parents_and_self` field is not recomputed when `parent_path` changes, despite the former depending on the latter.

Solution:
Ensure that `parents_and_self` is recomputed whenever `parent_path` is updated, so that the correct name is reflected in the breadcrumb.

Steps to reproduce:
- Open the form to create a new e-commerce category.
- After saving, the breadcrumb displays "Unnamed" instead of the actual category name.

opw-4267144

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

Forward-Port-Of: odoo/odoo#186929
Forward-Port-Of: odoo/odoo#184423

Before this commit, a user was able to double click on check-in/check-out. To avoid that the pop-up will be automatically closed when the button will be clicked. task-4316077 Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186565

Before this commit, a user was able to double click on check-in/check-out. To avoid that the pop-up will be automatically closed when the button will be clicked.

task-4316077

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Forward-Port-Of: odoo/odoo#186565

As so_reference_type can be left empty on the payment.provider, we need to handle the case in the back end and effectively allow an empty payment reference. With no payment reference defined on the sale.order (field reference), we have the possibility to let the invoice define the payment reference itself (field payment_reference) which allows an easier reconciliation of payments and invoices. opw-4282903 Forward-Port-Of: odoo/odoo#187205

As so_reference_type can be left empty on the payment.provider, we need to handle the case in the back end and effectively allow an empty payment reference.

With no payment reference defined on the sale.order (field reference), we have the possibility to let the invoice define the payment reference itself (field payment_reference) which allows an easier reconciliation of payments and invoices.

opw-4282903

Forward-Port-Of: odoo/odoo#187205

Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#187125 Forward-Port-Of: odoo/odoo#186755

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




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

Forward-Port-Of: odoo/odoo#187125
Forward-Port-Of: odoo/odoo#186755

To reproduce: Go to Accounting/Invoicing, Customers and create a new Customer. Delete it. You get an error talking about audit trail while you don't have it activated. The issue is that we block based on customer/supplier rank when there is no company on the partner. We now check if we should block the deletion of a message of a partner if this partner has at least one journal entry with a company that has audit trail activated. --- I confirm I have signed the CLA and read the

To reproduce:
Go to Accounting/Invoicing, Customers and create a new Customer. Delete it.
You get an error talking about audit trail while you don't have it activated.

The issue is that we block based on customer/supplier rank 
when there is no company on the partner.

We now check if we should block the deletion of a message of a 
partner if this partner has at least one journal entry with a 
company that has audit trail activated.

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

Forward-Port-Of: odoo/odoo#187151
Forward-Port-Of: odoo/odoo#181891

We have new coders --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#186749

We have new coders


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

Forward-Port-Of: odoo/odoo#186749