Customers paying for a subscription now see a clear warning when their company does not match the company linked to the subscription. This avoids hiding payment options entirely and helps users understand why there may be a company mismatch during payment.

Rather than hiding all payment providers and payment tokens from the
payment form, a warning is now shown to the user if their company is
not the same as that of the subscription they're paying for.

task-2983985

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

The Unread messages filter is now shown only to users who manage notifications inside Odoo, keeping it hidden for users who receive notifications by email. This reduces confusing or irrelevant options in Helpdesk and Field Service search views and makes notification-related filters more consistent across apps.

The goal of this revision is to add a group
`mail.group_mail_notification_type_inbox` which is granted automatically when the user `notification_type` is set to `Inbox` to be able to easily hide the filter `Unread messages` when the user uses the `Email` notification type,
by simply adding `groups="mail.group_mail_notification_type_inbox"` on the filter rather than overriding `_get_view` in every model.

The code overriding `_get_view` of `project.task`
to hide the filter "Unread messages" replaced
in this revision initially comes from
odoo/odoo@da868d28e2f1268acf0ee413f04ebf3554182249

> - In project.task search View:
>   - the filter for unread messages should be visible only if the current user
>     managing his notifications in Odoo

The above revision was part of the task 2844212

Adds alert box styling as part of a tutorial exercise to better understand Odoo's enterprise web styling structure. This is a minor internal improvement with limited direct business impact, focused on design framework familiarity.

This commit is a tutorial for mano. The purpose being to add an alert-box to familiarize with the SCSS structure of Odoo.

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

task-3078965

This change keeps Odoo spreadsheet features working correctly after an update to the underlying spreadsheet engine. It helps ensure spreadsheet documents, pivots, lists, charts, and autofill behavior continue to function as expected for users.

The Enterprise web module no longer includes old code for App Store and Updates menus that have already been removed. This keeps the product cleaner and avoids maintaining unused functionality, with no expected impact on users.

Menus "Apps Store" and "Updates" are deleted in CE, so the js file is not needed anymore.

See https://github.com/odoo/odoo/pull/106379

The appointment module was updated to remove outdated internal code from its public booking widgets. This keeps the booking experience aligned with current platform standards and reduces future maintenance risk without changing visible functionality for users.

See community commit for details.

Traceback when computing taxes using TaxCloud. Steps to reproduce: -Activate TaxCloud in accounting settings, with valids "API ID" and "API KEY". -Create an invoice for a USA customer with an invoice line and "Fiscal Position" set to "Automatic Tax Mapping (TaxCloud)" (in the "Other Info" tab). -Confirm -->Traceback Traceback: File "/src/enterprise/16.0/account_taxcloud/models/taxcloud_request.py", line 136, in get_all_taxes_values for item in response.CartItemsResponse.CartI

Traceback when computing taxes using TaxCloud.

Steps to reproduce:
-Activate TaxCloud in accounting settings, with valids "API ID" and
 "API KEY".
-Create an invoice for a USA customer with an invoice line and
 "Fiscal Position" set to "Automatic Tax Mapping (TaxCloud)" (in the
 "Other Info" tab).
-Confirm
-->Traceback

Traceback:
File
"/src/enterprise/16.0/account_taxcloud/models/taxcloud_request.py",
line 136, in get_all_taxes_values
for item in response.CartItemsResponse.CartItemResponse:
AttributeError: 'NoneType' object has no attribute 'CartItemResponse

Explanation:
-There's a traceback when CartItem is empty (like if there are no move
 lines).
-It is empty because of the filter in the function
 '_process_lines(self, lines)'.
 --> 'lines.filtered(lambda l: not l.display_type)'.
-The goal is to take only move lines that are not Notes or Sections.
-This worked in v15 because display_type was defined as:

    display_type = fields.Selection([
            ('line_section', 'Section'),
            ('line_note', 'Note'),
        ], default=False, help="Technical field for UX purpose.")

-But now in v16 it is defined as:

    display_type = fields.Selection(
            selection=[
                ('product', 'Product'),
                ('cogs', 'Cost of Goods Sold'),
                ('tax', 'Tax'),
                ('rounding', "Rounding"),
                ('payment_term', 'Payment Term'),
                ('line_section', 'Section'),
                ('line_note', 'Note'),
                ('epd', 'Early Payment Discount'),
            ],
            compute='_compute_display_type', store=True, readonly=False,
            precompute=True, required=True,
        )

-The display_type=False does not corresponds anymore to move lines
 that are not Sections or Notes, but it corresponds to no move lines at
 all.

The fix:
 Will filter move lines that are not of type 'line_section' or
 'line_note'.

Discussion:
 Do I fix the traceback that we get when there a no move lines?  This
 'issue' is present since at least v14 and it seems like nobody ever
 complained.

+:
 I've applied the similar change to some lines in the code that also
 check if 'display_type' is False for some 'account.move.line' records.

++:
 The fix revealed an other issue in the function
  '_inter_company_create_invoices' of the file
  enterprise/account_inter_company_rules/models/account_move.py:
  There's a call on a function that doesn't exist anymore
  'line._set_price_and_tax_after_fpos()'.  I've deleted the line.

opw-3064174

Forward-Port-Of: odoo/enterprise#34289

**Fedex** When sending a request to Fedex server, the UoM used for the dimensions is based on the UoM of the weight, which is defined on the carrier: https://github.com/odoo/enterprise/blob/e4fd13a0e073b9855864b7fabc26bc05b9a5fd19/delivery_fedex/models/fedex_request.py#L178 https://github.com/odoo/enterprise/blob/e4fd13a0e073b9855864b7fabc26bc05b9a5fd19/delivery_fedex/models/delivery_fedex.py#L96-L98 However, this is not that clear for the user as there isn't any information on client-si

**Fedex**

When sending a request to Fedex server, the UoM used for the dimensions
is based on the UoM of the weight, which is defined on the carrier:
https://github.com/odoo/enterprise/blob/e4fd13a0e073b9855864b7fabc26bc05b9a5fd19/delivery_fedex/models/fedex_request.py#L178
https://github.com/odoo/enterprise/blob/e4fd13a0e073b9855864b7fabc26bc05b9a5fd19/delivery_fedex/models/delivery_fedex.py#L96-L98
However, this is not that clear for the user as there isn't any
information on client-side about this.

**Easypost**

The label of the field is already displayed

OPW-3053048

Forward-Port-Of: odoo/enterprise#34248
Forward-Port-Of: odoo/enterprise#33754

This commit fixes a crash of the application when trying to open an article on which the user can only read, or when trying to open another article from one that he can only read. This was linked to the fact that the new `openArticle` function tried to access the emoji button of the said article even though it doesn't exist for the user that is only able to read. Now we check if the button exists before trying to modify it. task-3076075 Forward-Port-Of: odoo/enterprise#34275

This commit fixes a crash of the application when trying to open an article on which the user can only read, or when trying to open another article from one that he can only read.

This was linked to the fact that the new `openArticle` function tried to access the emoji button of the said article even though it doesn't exist for the user that is only able to read.

Now we check if the button exists before trying to modify it.

task-3076075

Forward-Port-Of: odoo/enterprise#34275

From the Accounting Dashboard, click on a journal (i.e. Miscellaneous Operations), then 'Favorites>Import records' and load a csv containing a journal entry Error: 'amount' is not in list This occurs since 45c67defa3cb853f73dfbc25d70cb285f1825dfe When user open the journal entries view, 'default_journal_id' is set in context and the data import process will try to parse bank statement data opw-3054896 Forward-Port-Of: odoo/enterprise#34246

From the Accounting Dashboard, click on a journal (i.e. Miscellaneous Operations),
then 'Favorites>Import records' and load a csv containing a journal entry

Error: 'amount' is not in list

This occurs since 45c67defa3cb853f73dfbc25d70cb285f1825dfe 
When user open the journal entries view, 'default_journal_id' is set in context 
and the data import process will try to parse bank statement data

opw-3054896

Forward-Port-Of: odoo/enterprise#34246