### Steps to reproduce: - Install Contacts app - Go to General Settings and add another language - Add a new contact to a parent. - Don't add a specific contact name - Assign a contact type (delivery address, invoice address, other address) - Go to the list or kanban view of the contacts and change the language - The type of the contact listed next to the parent name is not translated from English. ### Investigation: - When the contact name is not set, the `display_name`

### Steps to reproduce:

- Install Contacts app
- Go to General Settings and add another language
- Add a new contact to a parent. 
     - Don't add a specific contact name 
     - Assign a contact type (delivery address, invoice address, other address)
- Go to the list or kanban view of the contacts and change the language
- The type of the contact listed next to the parent name is not translated from English.

### Investigation:
- When the contact name is not set, the `display_name` displayed in both kanban and list views is set by concatenating the parent name with the contact type.
- The line https://github.com/odoo/odoo/blob/03b7e17faef4075dbbb805bca4e7f40f7fbcc988/odoo/addons/base/models/res_partner.py#L345 in the function `_compute_display_name`, `with_context({})` in particular basically enforce to compute the name in english language regardless of the active language. That actually makes sense as the `display_name` field has `store=True` https://github.com/odoo/odoo/blob/03b7e17faef4075dbbb805bca4e7f40f7fbcc988/odoo/addons/base/models/res_partner.py#L199

### Solution:
- add a computed field that is not stored that gets recomputed on changing the language.

opw-3569171

Forward-Port-Of: odoo/odoo#147650
Forward-Port-Of: odoo/odoo#143514

Steps: - In mobile open project - Project.project form view - Share project - Invite people, the 'email' is displayed twice in the kanban view Issue: - In mobile when project share invite people, the 'email' is displayed twice in the kanban view Cause: - This will be coming because of the context for show_email Fix: - By removing of context show_email it will be working fine. task-3550702 Forward-Port-Of: odoo/odoo#150528 Forward-Port-Of: odoo/odoo#140920

Steps:
- In mobile open project
- Project.project form view
- Share project
- Invite people, the 'email' is displayed twice in the kanban view

Issue:
- In mobile when project share invite people, the 'email' is displayed twice in the kanban view

Cause:
- This will be coming because of the context for show_email

Fix:
- By removing of context show_email it will be working fine.

task-3550702

Forward-Port-Of: odoo/odoo#150528
Forward-Port-Of: odoo/odoo#140920

With this change, we can set other conditions easily. Also, it allows us to check if it can be payed without actually executing the pay function, because sometimes we don't want to change the screen but we want to check if the order can be processed for payment. For example, we could disable the Pay Button from the Product Screen --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#150914

With this change, we can set other conditions easily.

Also, it allows us to check if it can be payed without actually executing the pay function,
because sometimes we don't want to change the screen but we want to check if the order can
be processed for payment.

For example, we could disable the Pay Button from the Product Screen

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

Forward-Port-Of: odoo/odoo#150914

**Before this commit:** When a user adds a tip and removes it by hitting multiple backspaces, a traceback occurs. The value passed as the tip was supposed to be an empty string if no tip is applied, but it received a null value, causing a traceback. **After this commit:** The tip value is checked to be a truthy value. If it is not a truthy value, then an empty string is passed, resolving the traceback. task-3692849 Forward-Port-Of: odoo/odoo#150586

**Before this commit:**
When a user adds a tip and removes it by hitting multiple backspaces, 
a traceback occurs. The value passed as the tip was supposed to be
an empty string if no tip is applied, but it received a null value, causing 
a traceback.

**After this commit:**
The tip value is checked to be a truthy value. If it is not a truthy value, 
then an empty string is passed, resolving the traceback.

task-3692849

Forward-Port-Of: odoo/odoo#150586

The change introduced in 72f7c0d7d16a1b avoids recomputes when there is nothing that needs to be written on a pos.config. However, starting v17 the way x2many are managed changed and while the command to assign values on x2many from settings was `[(6, 0, ids)]`, in v17 it's `[[4,id],...,[4,id]]`. The `SET` command was replaced by the `LINK` command. This changes the returned value of the `convert_to_cache` method and made it impossible to change pos_config.x2many values in v17 because of the

The change introduced in 72f7c0d7d16a1b avoids recomputes when there is nothing that needs to be written on a pos.config.

However, starting v17 the way x2many are managed changed and while the command to assign values on x2many from settings was `[(6, 0, ids)]`, in v17 it's `[[4,id],...,[4,id]]`. The `SET` command was replaced by the `LINK` command. This changes the returned value of the `convert_to_cache` method and made it impossible to change pos_config.x2many values in v17 because of the changes in 72f7c0d7d16a1b.

To fix that, move the `_keep_new_vals` method from res_config_settings to pos_config and use `_preprocess_x2many_vals_from_settings_view` to change link commands to unlink + link commands.

Steps to reproduce:
   - Install point_of_sale
   - Go to Settings > Point of Sale
   - Remove a payment method
   - Save
   - The payment method is still set on the pos.config.

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

Forward-Port-Of: odoo/odoo#150900

- Improved the UX of the product configurator. - Display of attribute name in orderline name. Previously, the user had to click on the checkbox or radio to select the option, clicking on the label didn't work. The attribute name was not displayed in the orderline name, only the values. Now the input has been replaced by a button, making it easier to use on touch-screen devices. The attribute name is displayed in the orderline name in the format `Size: M, Fabric: Leather`. task-363819

- Improved the UX of the product configurator.
- Display of attribute name in orderline name.

Previously, the user had to click on the checkbox or radio to select the option, clicking on the label didn't work.
The attribute name was not displayed in the orderline name, only the values.

Now the input has been replaced by a button, making it easier to use on touch-screen devices.
The attribute name is displayed in the orderline name in the format `Size: M, Fabric: Leather`.

task-3638192
task-3633555

Forward-Port-Of: odoo/odoo#147744

Currently the version of the cryptography module installed with the version of pyOpenssl 22.0.0 does not allow the execution of the Odoo server on the iot for versions 15, 16 and 17. With this change we explicitly give the version of the cryptography module 36.0.2 which corrects this problem. 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 w

Currently the version of the cryptography module installed with the version of pyOpenssl 22.0.0 does not allow the execution of the Odoo server on the iot for versions 15, 16 and 17.

With this change we explicitly give the version of the cryptography module 36.0.2 which corrects this problem.

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

Before this commit, since [1], the "small" class behavior of Bootstrap was changed to use a fixed value instead of being dependent on the context (using `em` units). This was a bad choice, given the fact that the "small" class could be used in the past with its previous behavior in custo but also in default Odoo layouts, where it could be use in more legit cases that the one Odoo currently offers: instead of applying the class to a whole paragraph, applying it to part of a title. In that cas

Before this commit, since [1], the "small" class behavior of Bootstrap was changed to use a fixed value instead of being dependent on the context (using `em` units).

This was a bad choice, given the fact that the "small" class could be used in the past with its previous behavior in custo but also in default Odoo layouts, where it could be use in more legit cases that the one Odoo currently offers: instead of applying the class to a whole paragraph, applying it to part of a title.
In that case, since [1], we can have a big title ... with a very small text next to it, which may be strange. Of course, the proper way to achieve a big title with a smaller text next to it would be to not use "small" but another hx font-size, but the legit bootstrap behavior which is to use their "small" class is thus broken.

This commit keeps the current possibilities (big title with very small text next to it) but does it by using new custom Odoo classes instead of changing the Bootstrap "small" one. That way, legit custo in previous versions (or trying to use default Bootstrap in this version) will be supported.

Note that this commit will impact existing 17.0 users though: if they actually configured a big title with small inner text... those will become big title with slightly smaller inner text (the default Bootstrap behavior). Worse: a big title whose size was reduced using the font-size selector and choosing "small" will now become a big title. We think this is worth the risk (see PR description for more visual details).

However, notice that "legit" use case of the "small" font-size in 17.0 will be kept untouched: e.g. adding a small text on its own or next to a paragraph: the "smaller" Bootstrap behavior is now computed based on the ratio of the configured base and small font-sizes.

Note that some additional "bugs" were found investigating this:
- Form descriptions use the "small" class for no reason and should probably not be possible to customize ("font style"-wise) anyway.
- The use of the "small" *tag* should probably be reviewed in all Odoo layouts and/or its interaction with the editor be fixed.

[1]: https://github.com/odoo/odoo/commit/194f73a9bbad8c3c3fb5c378e7bdfa704aaacdc0

| Before this PR | After this PR |
| -------- | -------- |
| ![default_before](https://github.com/odoo/odoo/assets/10338094/e3b49b7d-bc7f-4115-8145-56d19b1d147b)   | ![default_after](https://github.com/odoo/odoo/assets/10338094/9faa6f73-772e-4318-8ea3-ced2a51d0423)  |
| ![custo_before](https://github.com/odoo/odoo/assets/10338094/77a4824c-32a8-4b1e-a4d1-664b81d9e557)   | ![custo_after](https://github.com/odoo/odoo/assets/10338094/cb196592-7ff1-4927-b01d-0687cae50be5)   |

=> Legit use cases untouched, weird use cases impacted (should be rare, especially see also the weird margin-top in the second one), custo use case (@JKE-be 's case) solved.

Forward-Port-Of: odoo/odoo#149590

This commit adds misc changes to CoA, Taxes and Fiscal Positions. Task ID: 3672294 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#150969 Forward-Port-Of: odoo/odoo#149696

This commit adds misc changes to CoA, Taxes and Fiscal Positions. 

Task ID: 3672294

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

Forward-Port-Of: odoo/odoo#150969
Forward-Port-Of: odoo/odoo#149696

Prior to this commit, when adding a product to an order, navigating back to the floor screen, and subsequently reopening the table, clicking on "Order" would send the order to the preparation display again. The issue stemmed from the fact that "this" was being added to "ordersToUpdateSet" in posStore, whereas "order" should be added to that set. opw-3687977 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#150674

Prior to this commit, when adding a product to an order, navigating back to the floor screen, and subsequently reopening the table, clicking on "Order" would send the order to the preparation display again. The issue stemmed from the fact that "this" was being added to "ordersToUpdateSet" in posStore, whereas "order" should be added to that set.

opw-3687977

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

Forward-Port-Of: odoo/odoo#150674

Steps to reproduces: - Create two products one with UoM units and the other grams - Create and confirm an SO with these two products - Set quantities and validate the transfer - Click "Print labels" Bug: only products with UoM units are printed because "quantity_by_product" is overwritten with only those products moved qty Fix: print a single label for the other UoMs opw-3676642 Forward-Port-Of: odoo/odoo#151236 Forward-Port-Of: odoo/odoo#150407

Steps to reproduces:
- Create two products one with UoM units and the other grams
- Create and confirm an SO with these two products
- Set quantities and validate the transfer
- Click "Print labels"

Bug:
only products with UoM units are printed because "quantity_by_product" is overwritten with only those products moved qty

Fix:
print a single label for the other UoMs

opw-3676642

Forward-Port-Of: odoo/odoo#151236
Forward-Port-Of: odoo/odoo#150407

Current behaviour before commit: In a saved pad, putting cursor inside a link without making any other changes makes editor dirty. This happens because `sanitize` method fails to sanitize the clone node of root editable element. As result discard button appears on top. Desired behaviour after commit: Now, `sanitize` method sanitizes the clone node of root editable element. Due to this, putting cursor inside a link without editing doesn't make editor dirty and discard button doesn't

Current behaviour before commit:

In a saved pad, putting cursor inside a link without making any other changes makes editor dirty.
This happens because `sanitize` method fails to sanitize the clone node of root editable element.
As result discard button appears on top.

Desired behaviour after commit:

Now, `sanitize` method sanitizes the clone node of root editable element. Due to this, putting cursor 
inside a link without editing doesn't make editor dirty and discard button doesn't appear on top.

task-3607361



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

Forward-Port-Of: odoo/odoo#151094
Forward-Port-Of: odoo/odoo#143737

The tax with xmlid vat_0_import was missing its repartition lines which caused validation errors. This PR adds empty repartition lines to fix this problem. Forward-Port-Of: odoo/odoo#151052 Forward-Port-Of: odoo/odoo#150874

The tax with xmlid vat_0_import was missing its repartition lines which caused validation errors.
This PR adds empty repartition lines to fix this problem.

Forward-Port-Of: odoo/odoo#151052
Forward-Port-Of: odoo/odoo#150874

When flagging a post, moderators should see the flagged moderation queue counter appear/increment. We renamed the span in 21531bd9 and forgot to update this reference. Task-3349373 Forward-Port-Of: odoo/odoo#149645

When flagging a post, moderators should see the flagged moderation queue counter appear/increment.

We renamed the span in 21531bd9 and forgot to update this reference.

Task-3349373

Forward-Port-Of: odoo/odoo#149645

The import feature of matching numbers was done manually in all imports, but the generic import was missing. For instance, with this file: ```csv name,line_ids/account_id,line_ids/debit,line_ids/credit,line_ids/matching_number test 2,400000,,121,1 ,500000,121 test 1,400000,121,,1 ,451000,,21 ,700000,,100 ``` The system wouldn't understand that this is an imported number. Forward-Port-Of: odoo/odoo#150848

The import feature of matching numbers was done manually in all imports, but the generic import was missing.

For instance, with this file:
```csv
name,line_ids/account_id,line_ids/debit,line_ids/credit,line_ids/matching_number
test 2,400000,,121,1
,500000,121
test 1,400000,121,,1
,451000,,21
,700000,,100
```

The system wouldn't understand that this is an imported number.

Forward-Port-Of: odoo/odoo#150848

To reproduce: - Go in admin user - activate Audit Trail in the settings - Log out - Connect as demo - Go to the audit trail report - Activate the filter Update Only => Access right error The demo user doesn't have the right access for the domain of the filter. We should hide this filter for these users (Causes an issue in the click_all test) Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: ---

To reproduce:
- Go in admin user
- activate Audit Trail in the settings
- Log out
- Connect as demo
- Go to the audit trail report
- Activate the filter Update Only
 => Access right error

The demo user doesn't have the right access
for the domain of the filter.
We should hide this filter for these users

(Causes an issue in the click_all test)

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

Before this commit the button to add documents from an URL is labeled "Add Document" which is confusing given it is displayed besides an "Upload Document" button. This commit renames the "Add Document" button into "Add URL" to make its purpose more obvious. task-3493618 Forward-Port-Of: odoo/odoo#149406 Forward-Port-Of: odoo/odoo#136512

Before this commit the button to add documents from an URL is labeled "Add Document" which is confusing given it is displayed besides an "Upload Document" button.

This commit renames the "Add Document" button into "Add URL" to make its purpose more obvious.

task-3493618

Forward-Port-Of: odoo/odoo#149406
Forward-Port-Of: odoo/odoo#136512

The aim of this commit is to make the duplicate bill warning works in edit mode. This is a backport of some fixes that were done in the following commit: cb694599583f5df1667984fee01bbcc4c8b2d409 Before the commit: The warning couldn't be triggered in edit mode. After the commit: The warning is triggered as soon as the field is unfocused. task-id: None Forward-Port-Of: odoo/odoo#149416

The aim of this commit is to make the duplicate bill warning works in edit mode.
This is a backport of some fixes that were done in the following commit: cb694599583f5df1667984fee01bbcc4c8b2d409

Before the commit:
The warning couldn't be triggered in edit mode.

After the commit:
The warning is triggered as soon as the field is unfocused.

task-id: None

Forward-Port-Of: odoo/odoo#149416

Since 17.0 , calls to _get_combination_info on the /shop/cart page were removed to avoid recomputing values already stored on the cart, speeding up the page loading. See 824fc94bbcc6ea63b5416a2be59b860ef65714eb Nevertheless, this highlighted the difference in pricelist discount computation between sale and website_sale. In sale, the discount is computed while considering the base price of the pricelist, whereas for `website_sale`, the base price was always the sales price. To make s

Since 17.0 , calls to _get_combination_info on the /shop/cart page were removed to avoid recomputing
values already stored on the cart, speeding up the page loading.

See 824fc94bbcc6ea63b5416a2be59b860ef65714eb

Nevertheless, this highlighted the difference in pricelist discount computation between sale and website_sale.

In sale, the discount is computed while considering the base price of the pricelist, whereas for `website_sale`, the base price was always the sales price.

To make sure the crossed price displayed is the sales price as before on /shop/cart, we override the default sale behavior to force the sales price to be considered as price before the pricelist discount.


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

Forward-Port-Of: odoo/odoo#151321

Steps: - Install subscription and razorpay app. - Configure razorpay provider with tokenizable razorpay account. - Enable allow tokenize field. - create subscription with more then 100k and less then 500k amount. - Try to pay that subscription with razorpay. Issue: - Throwing limit exceed warning even though amount is less then 500k which can create token and paid normally. Cause: - We forgot to check minimum of method max amount and amount * 5 to send proper mandate max amount whi

Steps:
- Install subscription and razorpay app.
- Configure razorpay provider with tokenizable razorpay account.
- Enable allow tokenize field.
- create subscription with more then 100k and less then 500k amount.
- Try to pay that subscription with razorpay.

Issue:
- Throwing limit exceed warning even though amount is less then 500k which can create token and paid
normally.

Cause:
- We forgot to check minimum of method max amount and amount * 5 to send proper mandate max amount while creating token and because of that paying more then 100k via subscription raise error even to it should processed normally.

Fix:
- Check minimum of `method max amount` and `amount * 5` to send proper mandate max amount so it'll not raise error while paying amount in between 100k to 500k.

See also:
- https://github.com/odoo/enterprise/pull/55009

Forward-Port-Of: odoo/odoo#150410

When updating contracts, work entries are recomputed automatically for the employee linked to that contract. However some contracts might not have an employee, which raises an error. Added a check to recompute work entries only if the contract has an employee. Task: 3614495 Forward-Port-Of: odoo/odoo#150932 Forward-Port-Of: odoo/odoo#148419

When updating contracts, work entries are recomputed automatically for the employee linked to that contract. However some contracts might not have an employee, which raises an error.

Added a check to recompute work entries only if the contract has an employee.

Task: 3614495

Forward-Port-Of: odoo/odoo#150932
Forward-Port-Of: odoo/odoo#148419

Description of the issue/feature this PR addresses: The module `l10n_ch` after this commit https://github.com/odoo/odoo/commit/7a06ed07814ab8d9192d3a7ec15aba7f90f7294d will have deprecated `account_report_expression` with dependent external values, which causes ForeignKey Violation during the upgrade. Upgrade tries to remove that `expression` because it is deprecated but it has dependent external values. Current behavior before PR: Upgrade tries to remove that `expression` because it is d

Description of the issue/feature this PR addresses:
The module `l10n_ch` after this commit https://github.com/odoo/odoo/commit/7a06ed07814ab8d9192d3a7ec15aba7f90f7294d  will have deprecated `account_report_expression` with dependent external values, which causes ForeignKey Violation during the upgrade. Upgrade tries to remove that `expression` because it is deprecated but it has dependent external values. 

Current behavior before PR:
Upgrade tries to remove that `expression` because it is deprecated but it has dependent external values. 
It will happen to all db's which were on at least `16.0` version before that commit https://github.com/odoo/odoo/commit/7a06ed07814ab8d9192d3a7ec15aba7f90f7294d 

Desired behavior after PR is merged:
That deprecated external values will be deleted in upgrade.
In here I delete that external values in migration file and increased the version of module from `11.1`-->`11.2`

UPG-1203672


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

Forward-Port-Of: odoo/odoo#150650

**[FIX] sale_product_configurator: allow type False for customValue** Steps to reproduce(locally): 1) Create SO with the product that has a custom value attribute 2) Leave the custom field empty 3) Save SO and open product configurator again 4) Observe TypeError traceback Reason: customValue is supposed to be string but if value is not set, it remains False which cause a type error. After this commit: allow customValue be false **[FIX] sale_product_configurator: set value for no

**[FIX] sale_product_configurator: allow type False for customValue**

Steps to reproduce(locally):
1) Create SO with the product that has a custom value attribute
2) Leave the custom field empty
3) Save SO and open product configurator again
4) Observe TypeError traceback

Reason: customValue is supposed to be string but if value is not set,
it remains False which cause a type error.

After this commit: allow customValue be false

**[FIX] sale_product_configurator: set value for no_variant attribute**

Steps to reproduce:
1) Create product with an attribute that has several values and with an
attribute with 'create_mode = 'no_variant' and one value.
2) Create SO with this product, save
3) Open product configurator again and see the traceback

Reason: selected_attribute_value_id is not set.

After this commit: the attribure value is defined in get_values of
product configurator.

opw-3513685


**[FIX] sale_product_configurator,product: show archived combination**

Steps to reproduce:
1) Create SO with customizable product (example “Customizable Desk”)
2) Let default values in product configurator
3) Save SO
4) Go to product template, and in the Attribute remove all value
options, only leaving the custom value
5) Try to open the product in configurator in the saved SO

Reason:
archived combination is not loaded

After this commit:
When requested combination is archived, load it

opw-3513685

Forward-Port-Of: odoo/odoo#150653
Forward-Port-Of: odoo/odoo#146454

With this commit, the button "duplicate" when you selected some attendances is not shown anymore. task : 3646395 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#147276

With this commit, the button "duplicate" when you selected some attendances is not shown anymore.

task : 3646395

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

Implemented 'Codice Fiscale' field in checkout address form, addressing a key need for our Italian customers. This enhancement: - Adds an optional 'Codice Fiscale' field, available for both individuals and companies. - Ensures compliance with Italian e-invoice requirements. This update is a step towards better adapting our system to specific localization requirements, enhancing user experience in italy. task-3623622 --- I confirm I have signed the CLA and read the PR guideline

Implemented 'Codice Fiscale' field in checkout address form, addressing a key need for our Italian customers.

This enhancement:

- Adds an optional 'Codice Fiscale' field, available for both individuals and companies.
- Ensures compliance with Italian e-invoice requirements.

This update is a step towards better adapting our system to specific localization requirements, enhancing user experience in italy.

task-3623622


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

Forward-Port-Of: odoo/odoo#151472
Forward-Port-Of: odoo/odoo#147828

The author should always be notified when he cancels an appointment. The mail works as a proof that the cancellation has been taken into account. task-3505819 Forward-Port-Of: odoo/enterprise#55221 Forward-Port-Of: odoo/enterprise#47724

The author should always be notified when he cancels an appointment. The mail works as a proof that the cancellation has been taken into account.

task-3505819

Forward-Port-Of: odoo/enterprise#55221
Forward-Port-Of: odoo/enterprise#47724

**[FIX] l10n_mx_edi: Remove reference to account_edi** **[IMP] l10n_mx_edi: Get the Mexican timezone from the same method.** The timezone is hardcoded at multiple places. It's less error prone to get the timezone everywhere from the same method. **[FIX] l10n_mx_edi: Don't fetch twice certificate + fix empty root_company** The certificate was fetched first when checking the config of the company, then when finding the certificate to use when processing the cfdi. Also, when we try t

**[FIX] l10n_mx_edi: Remove reference to account_edi**

**[IMP] l10n_mx_edi: Get the Mexican timezone from the same method.**
The timezone is hardcoded at multiple places.
It's less error prone to get the timezone everywhere from the same method.

**[FIX] l10n_mx_edi: Don't fetch twice certificate + fix empty root_company**

The certificate was fetched first when checking the config of the company,
then when finding the certificate to use when processing the cfdi.

Also, when we try to send a CFDI when no certificate are configurated, a traceback is raised.
This is because the root_company is the one having some certificate. If no certificate, the
root_company is empty and then, an ensure_one raises an error.

sentry-4719634588,4729692933,4729689997

Forward-Port-Of: odoo/enterprise#54544

999001 and 999002 are no longer used for extraordinary income/expenses. This commit removes them from the domains of the corresponding report. Task ID: 3672294 Forward-Port-Of: odoo/enterprise#55081 Forward-Port-Of: odoo/enterprise#54491

999001 and 999002 are no longer used for extraordinary income/expenses.
This commit removes them from the domains of the corresponding report.

Task ID: 3672294

Forward-Port-Of: odoo/enterprise#55081
Forward-Port-Of: odoo/enterprise#54491

Before this commit: When a user attempts to upload a file other than pdf in the PDF split page, it gives a traceback. After this commit: Now, user can only upload pdf files. Task-3613032 Forward-Port-Of: odoo/enterprise#55266 Forward-Port-Of: odoo/enterprise#52225

Before this commit:
When a user attempts to upload a file other than pdf in the PDF split page, it gives a traceback.

After this commit:
Now, user can only upload pdf files.

Task-3613032

Forward-Port-Of: odoo/enterprise#55266
Forward-Port-Of: odoo/enterprise#52225

In this PR we improve the usability of a production payroll app where dashboard warnings might take a long time to load by loading them asynchronously using rpc calls. task-3597092 Forward-Port-Of: odoo/enterprise#55210

In this PR we improve the usability of a production payroll app where dashboard warnings might take a long time to load by loading them asynchronously using rpc calls.
task-3597092

Forward-Port-Of: odoo/enterprise#55210

Steps: - Install subscription app and razorpay provider. - Configure and publish razorpay provider. - Create a subscription and pay via razorpay. - Now change system date to next recurring date. Issue: - Subscription is in `Payment Failure` state even though payment is successfully captured. Cause: - Because of concurrent update in database while creating transaction from token for recurring charges - When razorpay make tokenize request via `_send_payment_request` method then

Steps:
- Install subscription app and razorpay provider.
- Configure and publish razorpay provider.
- Create a subscription and pay via razorpay.
 - Now change system date to next recurring date.

 Issue:
 - Subscription is in `Payment Failure` state even though payment is successfully captured.

 Cause:
 - Because of concurrent update in database while creating transaction from token for recurring charges
 - When razorpay make tokenize request via `_send_payment_request` method then transaction process data via `_handle_notification_data` and from web-hook so it tries to write on transaction with same data multiple times and at same time subscription also tries to write so because of concurrent update it skips to write on subscription and subscription stays in `Payment Failure` state.

 Fix:
 - Handle writing on subscription in there state changing method instead of trying to write in between when transaction processing so it does not skip writing on subscription and properly set/remove subscription state.

 task-3652228

Forward-Port-Of: odoo/enterprise#53792

…rder.log.report taskid: 3702648 Forward-Port-Of: odoo/enterprise#55102

…rder.log.report

taskid: 3702648

Forward-Port-Of: odoo/enterprise#55102

In large database when you unlink an attachment (during assets generate for exemple or unlink record with attachments) can be take 1 second. Forward-Port-Of: odoo/enterprise#54261 Forward-Port-Of: odoo/enterprise#54213

In large database when you unlink an attachment (during assets generate for exemple or unlink record with attachments) can be take 1 second.

Forward-Port-Of: odoo/enterprise#54261
Forward-Port-Of: odoo/enterprise#54213

Since 1st January 2024 the tax scale V has been added source: https://www.estv.admin.ch/estv/fr/accueil/impot-federal-direct/impot-a-la-source/baremes-is-salaires.html Forward-Port-Of: odoo/enterprise#55237

Since 1st January 2024 the tax scale V has been added 
source: https://www.estv.admin.ch/estv/fr/accueil/impot-federal-direct/impot-a-la-source/baremes-is-salaires.html

Forward-Port-Of: odoo/enterprise#55237

This commit add MRR in `_get_mandate_values` return dict to use it in at time of token creation to set max amount according to MRR of subscription. See also: - https://github.com/odoo/odoo/pull/150410 Forward-Port-Of: odoo/enterprise#55009

This commit add MRR in `_get_mandate_values` return dict to use it in at time of token creation to set max amount according to MRR of subscription.

See also:
- https://github.com/odoo/odoo/pull/150410

Forward-Port-Of: odoo/enterprise#55009

Forward-Port-Of: odoo/enterprise#55166

Forward-Port-Of: odoo/enterprise#55166

Before  After  Forward-Port-Of: odoo/enterprise#54587

Before
![image](https://github.com/odoo/enterprise/assets/7775116/967e8b0a-efa4-43b1-8754-90bfcccaeca8)

After

![image](https://github.com/odoo/enterprise/assets/7775116/99a2fe56-6ac8-45a5-a330-0e6cc5f87dab)

Forward-Port-Of: odoo/enterprise#54587