This change removes an unnecessary space in the accounting reports code. It is a small cleanup that helps keep the codebase tidy without changing how users interact with the system.

An useless space was inserted between option and
the strict equality. The aim of this commit is removing it forever.

no task id

This commit changes the behavior of inserting any embedded view inside of a knowledge article: when inserted we switch the view to full_width. This way it is easier to work with embedded views as they are bigger and easier to see. task-3604828 Forward-Port-Of: odoo/enterprise#52131

This commit changes the behavior of inserting any embedded view inside of a knowledge article: when inserted we switch the view to full_width. This way it is easier to work with embedded views as they are bigger and easier to see.

task-3604828

Forward-Port-Of: odoo/enterprise#52131

This commit fixes a bug where the name input would not resize when switching articles, leading to some titles being unreadable. Now each time that the article changes we resize the input to accomodate the new title. Remove the erroneous `t-esc` usage. Rectification of https://github.com/odoo/enterprise/commit/7ea555fc76ad85c536a7d22495da8603dba064ce Now that the topbar is a component, the span that is guaranteeing the width of the container of the article name input can be set with

This commit fixes a bug where the name input would not resize when switching
articles, leading to some titles being unreadable.

Now each time that the article changes we resize the input to accomodate the
new title.

Remove the erroneous `t-esc` usage.
Rectification of https://github.com/odoo/enterprise/commit/7ea555fc76ad85c536a7d22495da8603dba064ce

Now that the topbar is a component, the span that is guaranteeing the width of
the container of the article name input can be set with a `t-out` instruction
(the topbar is re-rendered each time the record changes). The previously used
`t-esc` instruction was erroneous as it does not do anything in an owl template.

task-3640726

Forward-Port-Of: odoo/enterprise#53665
Forward-Port-Of: odoo/enterprise#53649

### Steps to reproduce: Have more than 80 project active on your db, go to my timesheets/all timesheets (or activate the my project filter) views> list view > group by project > some of the group project will show 0 timesheets linked even tho they do have timesheets ### Issue: the empty groups that have timesheets should not be displayed at all ### Cause: The _group_expand_project_ids supposed to be only for the grid view also triggers for the other views, the read_group of the listview

### Steps to reproduce:
Have more than 80 project active on your db, go to my timesheets/all timesheets (or activate the my project filter) views> list view > group by project > some of the group project will show 0 timesheets linked even tho they do have timesheets

### Issue:
the empty groups that have timesheets should not be displayed at all

### Cause:
The _group_expand_project_ids supposed to be only for the grid view also triggers for the other views, the read_group of the listview has a base limit of 80 but with the group expand 100 groups are fetched by page so more "empty" project groups are fetched to fill the result

### Solution:
Local solution to test thoroughly, 
renamed the 'group_expand' keys in the My timesheet/ All timesheets/ my project filter/ timesheet_view_grid_by_project_no_section by 'grid_group_expand'

In the read_grid method we check if that 'grid_group_expand' is present in the context, if so it'll also add the 'group_expand' key in the context then do the read_grid custom expansion

The _group_expand_project_ids and _group_expand_employee_ids now need to have this 'group_expand' in their context so basically they can now only be triggered if the read_grid method has been triggered before. This ensures us that this group expand can't happen alone in the list/kanban/... views

**this solution should be reviewed since i wasn't able to trigger the _group_expand_project_ids when the grid_view is enabled, so it may be possible to completely deprecated the _group_expand_project_ids method (as well as the _group_expand_employee_ids)**

Ticket-3450175

Forward-Port-Of: odoo/enterprise#53521
Forward-Port-Of: odoo/enterprise#51615

After odoo/enterprise#38518, there are cases in which people uninstall `l10n_it_edi` so the following traceback is given when importing a PDF invoice (OCR): ``` File "/home/odoo/src/enterprise/saas-16.4/l10n_it_reports/models/account_move.py", line 9, in <lambda> lambda rec: self.env['account.edi.format']._check_filename_is_fattura_pa(rec.name) AttributeError: 'account.edi.format' object has no attribute '_check_filename_is_fattura_pa' ``` We move everything back to `l10n_it_edi`,

After odoo/enterprise#38518, there are cases in which people uninstall `l10n_it_edi` so the following traceback is given when importing a PDF invoice (OCR):

```
File "/home/odoo/src/enterprise/saas-16.4/l10n_it_reports/models/account_move.py", line 9, in <lambda>
    lambda rec: self.env['account.edi.format']._check_filename_is_fattura_pa(rec.name)
AttributeError: 'account.edi.format' object has no attribute '_check_filename_is_fattura_pa'
```

We move everything back to `l10n_it_edi`, ~~but the test will be excised.~~

Community PR: odoo/odoo#147370

Forward-Port-Of: odoo/enterprise#53452
Forward-Port-Of: odoo/enterprise#53333

In a Manufacturing Order based on a BoM, changing the qty values and then change the scheduled date will reset the qty to the bom ones. This should not be the case. odoo: https://github.com/odoo/odoo/pull/143496 opw-3568943 Forward-Port-Of: odoo/enterprise#52892 Forward-Port-Of: odoo/enterprise#51822

In a Manufacturing Order based on a BoM, changing the qty values and then change the scheduled date will reset the qty to the bom ones.

This should not be the case.

odoo: https://github.com/odoo/odoo/pull/143496

opw-3568943

Forward-Port-Of: odoo/enterprise#52892
Forward-Port-Of: odoo/enterprise#51822

Before this commit and it's community counter part [1], the pager wasn't displayed in the TimesheetTimerListView. This was due to a wrong interaction between two calls to useSubEnv and useChildSubEnv (more information available on [1]). The issue has been fixed directly in the framework, so this commit only adds a test. opw 3636182 Forward-Port-Of: odoo/enterprise#53342 Forward-Port-Of: odoo/enterprise#53286

Before this commit and it's community counter part [1], the pager wasn't displayed in the TimesheetTimerListView. This was due to a wrong interaction between two calls to useSubEnv and useChildSubEnv (more information available on [1]). The issue has been fixed directly in the framework, so this commit only adds a test.

opw 3636182

Forward-Port-Of: odoo/enterprise#53342
Forward-Port-Of: odoo/enterprise#53286

Spanish translation has been modified by commit bf81596aa7b36a9a08b9701a9fcdab3e30902349 This behavior makes spanish variant (maxico, uruguay, columbia, etc.) use the es_419.po instead of es.po. This commit renames the po files for the LATAM localizations so that translations work as expected. Also, it adds the es_419.po file to the UNSPSC so that both spanish and its variant can use the UNSPSC code translations. Initiated by customer issue: opw-3627465 Forward-Port-Of: odoo/enter

Spanish translation has been modified by commit
bf81596aa7b36a9a08b9701a9fcdab3e30902349

This behavior makes spanish variant (maxico, uruguay, columbia, etc.) use the es_419.po instead of es.po.

This commit renames the po files for the LATAM localizations so that translations work as expected.

Also, it adds the es_419.po file to the UNSPSC so that both spanish and its variant can use the UNSPSC code translations.

Initiated by customer issue:
opw-3627465

Forward-Port-Of: odoo/enterprise#52694

Before this commit, an error message appeared when clicking on creating a new contract. The problem was: a field linked to the fleet application was used without it being installed. This was fixed by moving the check to the l10n_be_he_payroll_fleet module task: 3522341 Forward-Port-Of: odoo/enterprise#51072

Before this commit, an error message appeared when clicking on creating a new contract.

The problem was: a field linked to the fleet application was used without it being installed.

This was fixed by moving the check to the l10n_be_he_payroll_fleet module

task: 3522341

Forward-Port-Of: odoo/enterprise#51072

lineNetFigure doesn't include the discount. If we don't subtract we end up setting the wrong `price_total` and `price_subtotal` on the invoice lines. The test has been adapted to include one line with a discount to test this case. opw-3627449 Forward-Port-Of: odoo/enterprise#52672

lineNetFigure doesn't include the discount. If we don't subtract we end up setting the wrong `price_total` and `price_subtotal` on the invoice lines. The test has been adapted to include one line with a discount to test this case.

opw-3627449

Forward-Port-Of: odoo/enterprise#52672

'Buchungstext' is supposed to hold the line label and not the move name (or ref). It implies that the idea of grouping the data by accounts + partner does not hold anymore (as we need to split by line label). We get rid of this grouping as it's a byproduct of trying to group the line of product with the line of tax and the receivable/payable. opw-3633926 Forward-Port-Of: odoo/enterprise#53664 Forward-Port-Of: odoo/enterprise#53539

'Buchungstext' is supposed to hold the line label and not the move name (or ref).
It implies that the idea of grouping the data by accounts + partner does not hold anymore (as we need to split by line label). 
We get rid of this grouping as it's a byproduct of trying to group the line of product with the line of tax and the receivable/payable.

opw-3633926

Forward-Port-Of: odoo/enterprise#53664
Forward-Port-Of: odoo/enterprise#53539

When the user enters specific terms in the command palette, and there is no article matching those terms, the system will display a helper that allows the user to quickly create a new article with the provided name. The helper will only be shown if the user has the permission to create a new article in the database. To verify this permission, the system will perform an RPC call to the server each time the helper needs to be displayed. In practice, it's highly unlikely for the user to lose the

When the user enters specific terms in the command palette, and there is no article matching those terms, the system will display a helper that allows the user to quickly create a new article with the provided name. The helper will only be shown if the user has the permission to create a new article in the database. To verify this permission, the system will perform an RPC call to the server each time the helper needs to be displayed.

In practice, it's highly unlikely for the user to lose the `create` privilege between two searches. Therefore, one can cache the result of the RPC call that checks if the user is allowed to create a new article. Caching this result should reduce the number of RPC calls triggered when the user types something in the search bar.

To implement the caching mechanism, we will simply use the `memoize` utility function to cache the promise checking the user's `create` privilege. The system will perform the RPC call on the first invocation, cache the promise, and reuse it for subsequent calls, thereby improving speed.

task-3603346

Forward-Port-Of: odoo/enterprise#53543

The default purchase tax could be set on a customer invoice when it matched the tax found by the OCR. Now, it will properly check `account_sale_tax_id` instead of `account_purchase_tax_id` for customer invoices. Forward-Port-Of: odoo/enterprise#53717 Forward-Port-Of: odoo/enterprise#53558

The default purchase tax could be set on a customer invoice when it matched the tax found by the OCR.

Now, it will properly check `account_sale_tax_id` instead of `account_purchase_tax_id` for customer invoices.

Forward-Port-Of: odoo/enterprise#53717
Forward-Port-Of: odoo/enterprise#53558

Forward-Port-Of: odoo/enterprise#53724

Forward-Port-Of: odoo/enterprise#53724

Forward-Port-Of: odoo/enterprise#53628 Forward-Port-Of: odoo/enterprise#47503

Forward-Port-Of: odoo/enterprise#53628
Forward-Port-Of: odoo/enterprise#47503