### Description of the issue/feature this PR addresses: We have demo data that is not a real case of use, and if we try to re-use the partner to invoice for the EDI module we will get an error. ### Current behavior before PR: We have a **Foreign Partner** from the United States have an identification type of Uruguay Resident (NIE). This is not a real case because if you are from outside of Uruguay you can not select the NIE document type or any document issued by the Uruguay government.

### Description of the issue/feature this PR addresses:

We have demo data that is not a real case of use, and if we try to re-use the partner to invoice for the EDI module we will get an error.

### Current behavior before PR:

We have a **Foreign Partner** from the United States have an identification type of Uruguay Resident (NIE). This is not a real case because if you are from outside of Uruguay you can not select the NIE document type or any document issued by the Uruguay government.

Also if we want to re-use the demo partner to create new invoices and test the Send and Print functionality we are not able to send emails because the partners do not have an email set.

### Desired behavior after PR is merged:

We fixed this in the demo so makes sense. Now we have two demo partners:

* Fix Foreign partner to a proper document type
* Add a new partner, Resident Alien, who is a foreign person living in Uruguay which is the proper case for the use of NIE document type.
* We add an email to the UY demo partner, this way we can use this partners to test send and print functionality.


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

Forward-Port-Of: odoo/odoo#166543

### Steps to reproduce: - Create a PO: - 1 x storable product 1 - 1 x storable product 2 - Confirm the PO - Change the quantity of the PO line of product 1 to 0 (this modifies the associated delivery accordingly) - Click on the customer to open the res.partner form - Click on the "On-Time Rate" smart button #### > Traceback: psycopg2.errors.DivisionByZero ### Cause of the issue: Clicking on that smart button will call the "_read_group" method and the following sql expressio

### Steps to reproduce:

- Create a PO:
  - 1 x storable product 1
  - 1 x storable product 2
- Confirm the PO
- Change the quantity of the PO line of product 1 to 0 (this modifies the associated delivery accordingly)
- Click on the customer to open the res.partner form
- Click on the "On-Time Rate" smart button

#### > Traceback: psycopg2.errors.DivisionByZero

### Cause of the issue:

Clicking on that smart button will call the "_read_group" method and the following sql expression will be added to the associated query: https://github.com/odoo/odoo/blob/b4620c123b753caf2b77472a8d6c42d767471c53/addons/purchase_stock/report/vendor_delay_report.py#L57-L60 The error is therefore rasied because the SUM(qty_total) associated to product 1 was reset to 0 because of our change on the PO line.

### Fix:

Since SUM(qty_total) of 0 signifies that no units of that product was not expected to be delivered for that customer. As such they should be removed from the products whose "On-Time Rate" is computed from the vendor.delay.report's.

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

Forward-Port-Of: odoo/odoo#166601
Forward-Port-Of: odoo/odoo#162632

Forward-Port-Of: odoo/odoo#166350

Forward-Port-Of: odoo/odoo#166350

Before this PR, using the blur feature during a call on the public page will display an error popup. The library used to do so is not loaded. This PR fixes the issue. task-3948111 Forward-Port-Of: odoo/odoo#166743 Forward-Port-Of: odoo/odoo#166707

Before this PR, using the blur feature during a call on the public page will display an error popup. The library used to do so is not loaded. This PR fixes the issue.

task-3948111

Forward-Port-Of: odoo/odoo#166743
Forward-Port-Of: odoo/odoo#166707

Steps to reproduce: > The Company Currency is the Dollar > Create a product > Set FIFO and Manual valuation > Set BIlling policy as Ordered Quantities > Create Purchase order in Euro > Create Vendor bill in USD (10 $) > Now Receive the quantities > Check the valuation > Wrong value (15.92 $) the value should be 10$ (taken from the bill) Bug: In the case of BIlling policy on Ordered Quantities and PO in a foreign currency we assume the bill will be in same currency as the PO Fix:

Steps to reproduce:
> The Company Currency is the Dollar
> Create a product > Set FIFO and Manual valuation
> Set BIlling policy as Ordered Quantities
> Create Purchase order in Euro
> Create Vendor bill in USD (10 $)
> Now Receive the quantities
> Check the valuation
> Wrong value (15.92 $)
the value should be 10$ (taken from the bill)

Bug:
In the case of BIlling policy on Ordered Quantities and PO in a foreign
currency we assume the bill will be in same currency as the PO

Fix:
currently unit price is first computed in PO currency and then converted
in the end to company currency added conversion from bill to PO
opw-[3805454](https://www.odoo.com/web#id=3805454&view_type=form&model=project.task)

also fixed a rounding issue opw-[3773413](https://www.odoo.com/web#id=3773413&view_type=form&model=project.task)

alternative fix:
compute everything in company currency (https://github.com/odoo/odoo/pull/155937)

Forward-Port-Of: odoo/odoo#166346
Forward-Port-Of: odoo/odoo#162827

### Issue: Trying to validate a wave transfer with an empty picking will raise and error. ### Expected behavior: The empty picking should be removed from the wave transfer and the rest of the operations should be validated. ### Steps to reproduce: - In the settings: enable Batch Transfers > Wave Transfers - Create 2 receipts: 1) 1 x product P1 2) 1 x product P2 - In the inventory overview, click on the dots of receipts > operations - Select your receipts > Add to w

### Issue:

Trying to validate a wave transfer with an empty picking will raise and error.

### Expected behavior:

The empty picking  should be removed from the wave transfer and the rest of the operations should be validated.

### Steps to reproduce:

- In the settings: enable Batch Transfers > Wave Transfers
- Create 2 receipts: 
    1) 1 x product P1 
    2) 1 x product P2
- In the inventory overview, click on the dots of receipts > operations
- Select your receipts > Add to wave >  Create new wave transfer
- Go to inventory > Operations > Transfers > Wave transfers
- Open your wave transfer  and set the quantity of P1 to 0

### Cause of the issue:

Currently, only the empty pickings 'waiting for another operation' are removed from the batch when it is validated:
https://github.com/odoo/odoo/blob/3cfe548ee03f96713c7a6d462409be9c825d22e7/addons/stock_picking_batch/models/stock_picking_batch.py#L201-L204 
In particlar, other empty pickings will not pass the sanity check: https://github.com/odoo/odoo/blob/3cfe548ee03f96713c7a6d462409be9c825d22e7/addons/stock_picking_batch/models/stock_picking_batch.py#L217-L218 and an operation error will be raised for them.

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

Forward-Port-Of: odoo/odoo#163320

**Current behavior:** In a multi-company environment, say we have a reusable box which has been used by multiple companies. While the box actively contains some product of companyA, companyB is not permitted to view their own stock transfers. **Expected behavior:** The current status of a package should not affect the accessibility of a company's picking history. **Steps to reproduce:** 1. Setup 2 companies, for both: Enable packages Enable stock warehouse locations

**Current behavior:**
In a multi-company environment, say we have a reusable box which has been used by multiple companies. While the box actively contains some product of companyA, companyB is not permitted to view their own stock transfers.

**Expected behavior:**
The current status of a package should not affect the accessibility of a company's picking history.

**Steps to reproduce:**
1. Setup 2 companies, for both:
        Enable packages
        Enable stock warehouse locations
        Enable multi-step routes -> set their in/out routes to 3-step (pick, pack, ship)

2. Create a reusable box type package, don't assign it to either company

3. In CompanyA, create a delivery using the reusable package and complete it so the package is fully emptied and ready to be reused

4. Switch to CompanyB, create a picking (any kind) using the same reusable box -don't finish the transfer- then switch back to CompanyA

5. Try to view Inventory transfers -> AccessError

**Cause of the issue:**
The delivery module adds the `_compute_shipping_weight()` method which is called on-demand when we try to open the transfers tree view. We will eventually look at packages from the picking that used the reusable package (which now 'belongs' to another company) and raise the AccessError.

**Fix:**
Use sudo() to read package records in the iteration over picking records.

We are only reading from pickings which belong to the current company, which makes the access check for the package records redundant (and as we see here problematic).

opw-3813917

Forward-Port-Of: odoo/odoo#166689
Forward-Port-Of: odoo/odoo#164677

### Steps to reproduce: - Inventory > Configuration > Warehouse Management > Operations types - Click on Manufacturing and put "Always" on create a backorder - Create a new MO for 2 units of a product and produce 1 unit #### > A wizzard appears to ask you if you want to create a backorder ### Cause of the issue: Clicking on the produce button will call the "button_mark_done" method. However, the parameters of backorder creations are not checked before the wizzard generation: https

### Steps to reproduce:

- Inventory > Configuration > Warehouse Management > Operations types
- Click on Manufacturing and put "Always" on create a backorder
- Create a new MO for 2 units of a product and produce 1 unit

#### > A wizzard appears to ask you if you want to create a backorder

### Cause of the issue:

Clicking on the produce button will call the "button_mark_done" method. However, the parameters of backorder creations are not checked before the wizzard generation:
https://github.com/odoo/odoo/blob/5c2f60ae2b8eb6699bd322bc4ea3d5054c7aea37/addons/mrp/models/mrp_production.py#L2118-L2120 will call the

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

Forward-Port-Of: odoo/odoo#164560

**Current behavior before PR:** if a partner is a member of any channel (eg, whatsapp channel) it will be displayed in the command palette even if he does not have any associated user.which will cause issues as you can not chat with partner who do not have any dedicated user. **Desired behavior after PR is merged:** partners with no dedicated users will not be displayed in the command palette to chat with when you enter @​. Task-3815150 --- I confirm I have signed the CLA and rea

**Current behavior before PR:**

if a partner is a member of any channel (eg, whatsapp channel) it will be displayed in the command palette even if he does not have any associated user.which will cause issues as you can not chat with partner who do not have any dedicated user.

**Desired behavior after PR is merged:**

partners with no dedicated users will not be displayed in the command palette to chat with when you enter @​.

Task-3815150

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

Forward-Port-Of: odoo/odoo#166220
Forward-Port-Of: odoo/odoo#159239

Inside our `_fetchQuiz` we pass the markup() to the quiz description to check that the description we have introduced is safe to be converted into html, the problem is that this markup() is not handling properly when the value of `quiz_data.slide_description` is false, so instead of not displaying anything we are sending a string of 'false'. Steps to reproduce: 1. Create quiz-type content inside a course in the e-learning app. 2. Do not add a description to the quiz. 3. Go to the website p

Inside our `_fetchQuiz` we pass the markup() to the quiz description to check that the description we have introduced is safe to be converted into html, the problem is that this markup() is not handling properly when the value of `quiz_data.slide_description` is false, so instead of not displaying anything we are sending a string of 'false'.

Steps to reproduce:
1. Create quiz-type content inside a course in the e-learning app.
2. Do not add a description to the quiz.
3. Go to the website page of the course.
4. Open the quiz in fullscreen.
5. A "false" message is displayed on the top-left corner.

opw-3887445

Forward-Port-Of: odoo/odoo#164549

Current behavior: When an iot device is linked to the PoS and invoice report, you had an error because action service and iot_websocket service where not available. Steps to reproduce: - Install pos_iot - Set an iot_device printer on the pos session - Set an iot_device on the report of the invoice - Open session, make an order and invoice it - You get an error opw-3792576 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo

Current behavior:
When an iot device is linked to the PoS and invoice report, you had an error because action service and iot_websocket service where not available.

Steps to reproduce:
- Install pos_iot
- Set an iot_device printer on the pos session
- Set an iot_device on the report of the invoice
- Open session, make an order and invoice it
- You get an error

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

Forward-Port-Of: odoo/odoo#165798

Suppose a SO line of 1210 with: t1 fixed tax of 5, price include, affect base amount t2 21% price included tax Make a down payment of 200. The resulting created SO line is computed as (1210 + 5) * (200 / 1210) = 200.83 instead of 200.0. 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#16678

Suppose a SO line of 1210 with:
t1 fixed tax of 5, price include, affect base amount t2 21% price included tax

Make a down payment of 200.
The resulting created SO line is computed as (1210 + 5) * (200 / 1210) = 200.83 instead of 200.0.

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#166787

Before this commit, you can delete an user linked to an employee without any warning. With this constraint, you need to manually remove the user on the employee record, so it cannot be done by accident. Forward-Port-Of: odoo/odoo#166516

Before this commit, you can delete an user linked to an employee without any warning. With this constraint, you need to manually remove the user on the employee record, so it cannot be done by accident.

Forward-Port-Of: odoo/odoo#166516

When the CRM module is installed, people can use the /lead command to create a new lead from a conversation. When using that command, the Odoo bot will log a message in the chat with a link to the newly created lead. When people click on that link, they will be redirected to the lead form view and will lose track of the conversation they have with the customer. To avoid that, we will now open a chat window of the active conversation when clicking on the internal link. People will then be able

When the CRM module is installed, people can use the /lead command to create a new lead from a conversation. When using that command, the Odoo bot will log a message in the chat with a link to the newly created lead. When people click on that link, they will be redirected to the lead form view and will lose track of the conversation they have with the customer.

To avoid that, we will now open a chat window of the active conversation when clicking on the internal link. People will then be able to quickly answer the client from the chat window.

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

Forward-Port-Of: odoo/odoo#161265

Steps to reproduce the bug: - In Website edit mode. - Drop 2 "Columns" snippets. - Hide one of the columns in the first snippet by clicking on the "Hide on desktop" button of the "Column" options in the side panel. - Start to drag another snippet. - Bug: There is no dropzone between the 2 "Column" snippets. The issue happens because when the column becomes invisible, after clicking the button, the attribute `data-invisible="1"` is added to the column in the DOM thanks the 'snippet_o

Steps to reproduce the bug:

- In Website edit mode.
- Drop 2 "Columns" snippets.
- Hide one of the columns in the first snippet by clicking on the "Hide
on desktop" button of the "Column" options in the side panel.
- Start to drag another snippet.
- Bug: There is no dropzone between the 2 "Column" snippets.

The issue happens because when the column becomes invisible, after
clicking the button, the attribute `data-invisible="1"` is added to the
column in the DOM thanks the 'snippet_option_visibility_update' event.

However, this event then propagates to the column's parent elements
(`<section>` and `<main>`). So, the attribute `data-invisible="1"` is also
added to the `<section>`, causing the dropzone not to be inserted as
expected. We should investigate this further later because it doesn't
seem consistent. For now, we prefer not to make changes at this level to
avoid introducing other bugs.

In this commit, we change the selector that determines where not to
insert dropzones so that it no longer considers `data-invisible="1"`.
This was added by this commit [1], but it seems unnecessary, and
':not(:visible)' in the selector is sufficient to avoid placing
dropzones between two non-visible elements.

[1]: https://github.com/odoo/odoo/commit/f9bd3033b21dbd1e4487d6d6cd1d8d8fdfbfb2ac

Forward-Port-Of: odoo/odoo#165797

- Previously,Odoo considers the invoice address as the place of supply. However, according to GST regulations, the place of supply may not always be the same as the invoice address. For movable goods, it should be the place of delivery and for Bill-to-Ship-to transactions, it should be the invoice address. - In situations other than Bill-to-Ship-to transactions, choose customer's delivery address as place of supply. task-3715853 Forward-Port-Of: odoo/odoo#160448

- Previously,Odoo considers the invoice address as the place of supply. However, according to GST regulations, the place of supply may not always be the same as  the invoice address. For movable goods, it should be the place of delivery and  for Bill-to-Ship-to transactions, it should be the invoice address.

- In situations other than Bill-to-Ship-to transactions, choose customer's delivery address as place of supply.

task-3715853

Forward-Port-Of: odoo/odoo#160448

In september 2023 7422eb643c5922bde8c70edfbe7b6f8dad53c1d9 replaced this._rpc by `this.bindService("rpc")`. In may 2024 58324ee59946c7bfe9970b5202cce8d4a36a69b0 was forward-ported without adaptating it to the new way rpc is used. This is causing report of an error in some case when using stripe express checkout. note: in saas-17.1 the code has to be changed again to `await rpc`. opw-3917632 Forward-Port-Of: odoo/odoo#166602

In september 2023 7422eb643c5922bde8c70edfbe7b6f8dad53c1d9 replaced
this._rpc by `this.bindService("rpc")`.

In may 2024 58324ee59946c7bfe9970b5202cce8d4a36a69b0 was
forward-ported without adaptating it to the new way rpc is used.

This is causing report of an error in some case when using stripe
express checkout.

note: in saas-17.1 the code has to be changed again to `await rpc`.

opw-3917632

Forward-Port-Of: odoo/odoo#166602

Currently, if you select a product that has variants, the popup window to choose the variants shows both active and inactive variants. Steps to reproduce: ------------------- * Make a quotation with the product `Desk Organizer` and select `Plastic` as its variant -> Confirm * Go to **Products** * Select `Desk Organizer` * Go to `Attributes & Variants` * Remove the `Plastic` option > The variant is now inactive * Go to the **Point of Sale** App * Open a shop session * Select the `D

Currently, if you select a product that has variants, the popup window to choose the variants shows both active and inactive variants.

Steps to reproduce:
-------------------
* Make a quotation with the product `Desk Organizer` and select `Plastic` as its variant -> Confirm
* Go to **Products**
* Select `Desk Organizer`
* Go to `Attributes & Variants`
* Remove the `Plastic` option
  > The variant is now inactive
* Go to the **Point of Sale** App
* Open a shop session
* Select the `Desk Organizer` product
> Observation: the `Plastic` variant is shown

Why the fix:
------------
We compare the workflow with sales, when doing a new quotation with the `Desk Organizer` product, the inactive variant is not an option to select.

We now load the information about attribute values being active or not when loading the data to the POS Session. All attributes that are inactive will not be shown in the product configurator.

opw-3713374

Forward-Port-Of: odoo/odoo#166491
Forward-Port-Of: odoo/odoo#165110

Issue: In the upgraded version, we have implemented the condition vals['name'] == _('New'). However, the data type of the 'name' field is character and translate = False. Additionally, the default value for the 'name' field is set to 'New', causing this condition to evaluate to false and consequently terminating the execution of the if block. Solution: To address this, we propose changing the condition to vals['name'] == 'New'

Issue: In the upgraded version, we have implemented the condition vals['name'] == _('New').
           However, the data type of the 'name' field is character and translate = False.
           Additionally, the default value for the 'name' field is set to 'New', causing
           this condition to evaluate to false and consequently terminating the execution
           of the if block.

    Solution: To address this, we propose changing the condition to vals['name'] == 'New'
              to ensure correct comparison. This modification is warranted due to the
              [configuration](https://github.com/odoo/odoo/blob/89fbb75659ba71b8c76dddd62ba331966161f59b/addons/repair/models/repair.py#L31)
              of the field:

              The field is not translatable.
              The field is required and set to readonly true, preventing customers from inputting values.
              The default value for the field is set to 'New'.

    Before:
           Unable to obtain the auto-generated sequence (receiving default value 'New').

    After:
          The sequence is generated automatically.

    OPW-3887638

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

Forward-Port-Of: odoo/odoo#165771

Steps to reproduce: ------------------- - create an employee at a time (E) - create a public holiday at some point in the future (PH) - create a user linked to the employee (U) With E < PH < U Issue: ------ The user has no timesheets linked to him/her, even though the employee was already present. As a result, the user does not see the timesheet in the timesheet grid. Solution: --------- Update the timesheet `user_id` field if an employee's user is modified. opw-3876732

Steps to reproduce:
-------------------
- create an employee at a time (E)
- create a public holiday at some point in the future (PH)
- create a user linked to the employee (U)

With E < PH < U

Issue:
------
The user has no timesheets linked to him/her,
even though the employee was already present.

As a result, the user does not see the timesheet
in the timesheet grid.

Solution:
---------
Update the timesheet `user_id` field
if an employee's user is modified.

opw-3876732

Forward-Port-Of: odoo/odoo#166578
Forward-Port-Of: odoo/odoo#166189

Create an asset for 2400$, acquisition date on 1/1/2023. Reevaluate it on 31/12/2023, 36 montths (+12) and add 1200$ to the amount. => The entries on the parent asset finish way too early. You don't get 36 months of lifetime. We would expect the amount of each new depreciation to be 50, so the amount of the parent + the child equals 100 each month for 36 months The reason why it happened is that we tried to compute the expected amount after each depreciation. This took into accoun

Create an asset for 2400$, acquisition date on 1/1/2023. 
Reevaluate it on 31/12/2023, 36 montths (+12) and add 1200$ to the amount.

=> The entries on the parent asset finish way too early. 
You don't get 36 months of lifetime.
We would expect the amount of each new depreciation to be 50, 
so the amount of the parent + the child equals 100 each month for 36 months

The reason why it happened is that we tried to compute the expected amount after each depreciation. 
This took into account changes of amount, but not changes of length.
We don't have a good way to incorporate changes of length in the old computation. 
To fix this, for linear, we consider the original amount from the beginning/the reevaluation to compute the amount for each period.

It does not hold for degressive_then_linear, so we separate the logic.

opw-3811165

Forward-Port-Of: odoo/enterprise#62377

__Current behavior before commit:__ When there is an incoming call, a VoIP provider may give a session description containing an audio sender and a video sender even if the video track is empty. In such case, `track` may be `null`. Therefore the page will crash when we try to set `track.enabled`. __Description of the fix:__ Check if each track is not `null` before setting its `enabled` property. opw-3833811 Forward-Port-Of: odoo/enterprise#62980

__Current behavior before commit:__
When there is an incoming call, a VoIP provider may give a session description containing an audio sender and a video sender even if the video track is empty.

In such case, `track` may be `null`. Therefore the page will crash when we try to set `track.enabled`.

__Description of the fix:__
Check if each track is not `null` before setting its `enabled` property.

opw-3833811

Forward-Port-Of: odoo/enterprise#62980

Steps to reproduce: - Create a contact who has the "City" and "State" populated, that would exceed 40 characters in the following format: "[City], [State] ([Country Code])" eg: "Marche-lez-Ecaussinnes, Brabant Wallon (BE)" - Enable Bpost and enter test credentials. - Create a Sales Order and add Bpost shipping. - Try to validate the transfer - Error about the "LocalityCode" being too long. Fix: same as for other fields impose max length limit opw-3895123 Forward-Port-Of: odoo/enter

Steps to reproduce:
- Create a contact who has the "City" and "State" populated, that would exceed 40 characters in the following format: "[City], [State] ([Country Code])"
eg: "Marche-lez-Ecaussinnes, Brabant Wallon (BE)"
- Enable Bpost and enter test credentials.
- Create a Sales Order and add Bpost shipping.
- Try to validate the transfer
- Error about the "LocalityCode" being too long.

Fix:
same as for other fields impose max length limit

opw-3895123

Forward-Port-Of: odoo/enterprise#62710

Include the version of Odoo in the UserAgent header of SIP requests so that the information is available to the provider. Task-3940569 Forward-Port-Of: odoo/enterprise#63127 Forward-Port-Of: odoo/enterprise#62879

Include the version of Odoo in the UserAgent header of SIP requests so that the information is available to the provider.

Task-3940569

Forward-Port-Of: odoo/enterprise#63127
Forward-Port-Of: odoo/enterprise#62879

Current behavior: When an iot device is linked to the PoS and invoice report, you had an error because action service and iot_websocket service where not available. Steps to reproduce: - Install pos_iot - Set an iot_device printer on the pos session - Set an iot_device on the report of the invoice - Open session, make an order and invoice it - You get an error opw-3792576 Forward-Port-Of: odoo/enterprise#61697

Current behavior:
When an iot device is linked to the PoS and invoice report, you had an
error because action service and iot_websocket service where not
available.

Steps to reproduce:
- Install pos_iot
- Set an iot_device printer on the pos session
- Set an iot_device on the report of the invoice
- Open session, make an order and invoice it
- You get an error

opw-3792576

Forward-Port-Of: odoo/enterprise#61697

The number of months worked in the previous year was not including previous occupations. Thus, the commissions were not added as the number of months was 0. Forward-Port-Of: odoo/enterprise#63160

The number of months worked in the previous year was not including previous occupations. Thus, the commissions were not added as the number of months was 0.

Forward-Port-Of: odoo/enterprise#63160

To reproduce: Create an asset. Reevaluate, with an increase, last month. => the move of Value Increase has today's date. We decided to instead put the acquisition date of the child asset. (so it won't be the same in 16.0) opw-3922067 Forward-Port-Of: odoo/enterprise#63115 Forward-Port-Of: odoo/enterprise#63097

To reproduce:
Create an asset.
Reevaluate, with an increase, last month.
=> the move of Value Increase has today's date.
We decided to instead put the acquisition date of the child asset. (so it won't be the same in 16.0)

opw-3922067

Forward-Port-Of: odoo/enterprise#63115
Forward-Port-Of: odoo/enterprise#63097

TaskID: 3942303 Forward-Port-Of: odoo/enterprise#62956

TaskID: 3942303

Forward-Port-Of: odoo/enterprise#62956

opw-3921760 opw-3889677 Forward-Port-Of: odoo/enterprise#63104 Forward-Port-Of: odoo/enterprise#62859

opw-3921760
opw-3889677

Forward-Port-Of: odoo/enterprise#63104
Forward-Port-Of: odoo/enterprise#62859