Account reports now show long text more predictably, with expanded text shown only when users click the relevant report cell. Report lines also use available column space more efficiently, making key names and labels easier to read without disrupting other report actions.

[IMP] account_report : ellipsis on reports

The way ellipsis works for the user on account reports changes :
- Clicking on a line does not unfold it. The user needs to click on the caret;
- Clicking on an anchor does not trigger the dropdown. The user needs to click on the vertical-ellispis icon on the right;
- Focusing on a line does not trigger the unfold of the ellipsis text. The user needs to click on the line.

To optimize the size of the text of the first column on the report, we process each line of the report to adjust the colspan of the line. By level of indentation, we figure out were is the next column with text and we make the first column use all the space available by increasing its colspan.

Ellipsis is now calculated dynamically. When there is a click on a report cell, we check (with js) if the text is longer than the parent container and then unfold the text.

Task-id : 2925918

Signed-off-by: Ruben Gomes rugo@odoo.com

This update keeps the Field Service inventory module aligned with a related platform change in Odoo. It is an internal compatibility improvement that helps ensure stock movements continue to work correctly after the shared function signature was updated.

This commit uses the the new function signature done in the community PR: odoo/odoo#116803

Timesheet grids now show empty rows for tasks assigned to the current user when their planned dates fall within the selected period, making it easier to log time directly. The update also adds safeguards so empty rows appear only where appropriate, including support for other employees in forecast views while avoiding unsuitable service or ticket records.

This commit display empty line in grid for task assigned to current user that has planned dates falling in span of grid and display empty line in todays grid for open tickets assigned to current user.

task-3077292

A small issue in the timesheet grid test setup was corrected so copied setup data is registered properly. This helps keep automated checks reliable and reduces the risk of regressions reaching users.

community: https://github.com/odoo/odoo/pull/130461

The barcode app now shows the finished product and any byproducts when scrapping items from a completed manufacturing order, instead of showing the raw components. This helps warehouse and production users identify the right items and reduces confusion during scrap operations.

Before this commit
==================
barcode app displays components instead of products in the scrap for MO in the done state.

After this commit
=================
With this commit barcode app displays main products and byproduct instead of components in the scrap for MO in the done state.

task - 3429322

This fixes an internal automated test setup for the accounting workflow between invoicing and accounting. It helps keep quality checks reliable after a recent technical change, reducing the risk of false failures during development.

The import system has changed, so the override is not working.
(https://github.com/odoo/enterprise/commit/5a800d5e304d02e15def04ef76911543c633af92)
We still need this import, even if we're just patching the registry,
if the test is deactivated.

Linked to runbot error 23638

The data merge list now refreshes correctly after merge-related actions following an internal model change. This prevents outdated or incorrect values from remaining visible, helping users see accurate information without disruption.

Since the relational model was rewritten (PR 114024), the removeRecord and removeGroup functions no longer exist.

In this case, reloading the model is sufficient to display the correct values.

This update adapts several Enterprise modules to a revised web framework mechanism used for extending behavior. It should not change day-to-day workflows, but it helps keep accounting, appointment, approvals, and related features compatible and maintainable.

This PR is the counterpart of https://github.com/odoo/odoo/pull/125716

task 3410198

This update removes old QWeb-based code from several Odoo Enterprise apps and moves affected screens and widgets toward newer frontend patterns. Users should see little to no immediate change, but the cleanup helps keep appointment booking, knowledge, helpdesk, payroll, social, VoIP, and website features easier to maintain going forward.

Issue: ====== When you download a document with a date in it's name and the date has dots (.) it will mess the with file at it expects the type of the file after the first dot. Steps to reproduce the error : ============================== 1-Install accounting 2-Install German Language 3-Go to accounting/customer/followup reports 4-Select an item and do follow up 5-Print the report. 6-You will get a report not in the pdf format. Solution: ========= I replaced the '.' with '/' in

Issue:
======
When you download a document with a date in it's name and the date has dots  (.) it will mess the with file at it expects the type of the file after the first dot.

Steps to reproduce the error :
==============================
1-Install accounting
2-Install German Language
3-Go to accounting/customer/followup reports
4-Select an item and do follow up
5-Print the report.
6-You will get a report not in the pdf format.

Solution:
=========
I replaced the '.' with '/' in the date formats of the name.

opw-3425241

Forward-Port-Of: odoo/enterprise#44932

Currently we take the language of the user generating the payslip, instead of taking the employee's language, which might be different. task-3389231 Forward-Port-Of: odoo/enterprise#44942 Forward-Port-Of: odoo/enterprise#43272

Currently we take the language of the user generating the payslip, instead of taking the employee's language, which might be different.

task-3389231

Forward-Port-Of: odoo/enterprise#44942
Forward-Port-Of: odoo/enterprise#43272

In the community PR, we have made several minor changes to improve the display, and this PR continues to build upon those improvements. Here's a summary of what has been done: - In the bank journal, an empty div was added by "account_online_synchronization" which caused some display issues with "qif_decimal_point" and "qif_qif_date_format." By adding the missing "attrs invisible" attribute, the display issue is now resolved. - In the settings, there was a field followed by a refresh bu

In the community PR, we have made several minor changes to improve the display,
and this PR continues to build upon those improvements. Here's a summary of what has been done:

- In the bank journal, an empty div was added by
"account_online_synchronization" which caused some display issues with
"qif_decimal_point" and "qif_qif_date_format." By adding the missing "attrs
invisible" attribute, the display issue is now resolved.

- In the settings, there was a field followed by a refresh button, but the input
 field was not aligned properly with the rest of the settings.

- Additionally, in the settings, the button links were not consistent with the
changes made in the community PR. This PR addresses that inconsistency and
brings uniformity to the button links.

task-id: 3342969

Forward-Port-Of: odoo/enterprise#42216

community: - https://github.com/odoo/odoo/pull/129991 task-3439555 part of task-3326263 Forward-Port-Of: odoo/enterprise#44758

community:
- https://github.com/odoo/odoo/pull/129991

task-3439555
part of task-3326263

Forward-Port-Of: odoo/enterprise#44758

Adds Balance Sheet and Profit and Loss for Canadian localization task-3098316 Forward-Port-Of: odoo/enterprise#44479

Adds Balance Sheet and Profit and Loss for Canadian localization

task-3098316

Forward-Port-Of: odoo/enterprise#44479

- Create Taiwan Accounting Reports task-2865568 Forward-Port-Of: odoo/enterprise#44875 Forward-Port-Of: odoo/enterprise#31818

- Create Taiwan Accounting Reports

task-2865568

Forward-Port-Of: odoo/enterprise#44875
Forward-Port-Of: odoo/enterprise#31818

Forward-Port-Of: odoo/enterprise#44478

Forward-Port-Of: odoo/enterprise#44478

- In certain specific values, the calculation of the withholding taxes are affected by the rounding configuration 'round globally' creating a variation of 0.01 cents in the calculation of the field l10n_ec_withhold_tax_amount - This results in a difference between the totals for withholding tax lines and the lines in the accounting entries in the withholding - To avoid this problem, we ensure to send the 'round' variable as True by context in withholding taxes to force 'round per line' **De

- In certain specific values, the calculation of the withholding taxes are affected by the rounding configuration 'round globally' creating a variation of 0.01 cents in the calculation of the field l10n_ec_withhold_tax_amount
- This results in a difference between the totals for withholding tax lines and the lines in the accounting entries in the withholding
- To avoid this problem, we ensure to send the 'round' variable as True by context in withholding taxes to force 'round per line'

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

-The 'Round globally' setting in the company produces an erroneous rounding in the amount of the withholding lines, causing a variation of one cent compared to the accounting entries

**Current behavior before PR:**
In some specific values, the value of the withholding amount varies with one cent to the accounting entry

**Desired behavior after PR is merged:**
Force 'Rounding per line' to ensure the correct calculation in withholdings

Forward-Port-Of: odoo/enterprise#43843
Forward-Port-Of: odoo/enterprise#43404

momentToLuxon was removed in community, and is replaced by a util function in website_sale_renting for the datetimepicker. This commit fixes the import from the right file. Forward-Port-Of: odoo/enterprise#44980

momentToLuxon was removed in community, and is replaced by a util function in website_sale_renting for the datetimepicker. This commit fixes the import from the right file.

Forward-Port-Of: odoo/enterprise#44980

Before, the only ordering that was made there put the reports without a country after the ones who had one. This was not consistent with the new sequence field introduced on account.report in saas-16.4. We fix that in order to make use of it. Forward-Port-Of: odoo/enterprise#44956

Before, the only ordering that was made there put the reports without a country after the ones who had one. This was not consistent with the new sequence field introduced on account.report in saas-16.4. We fix that in order to make use of it.

Forward-Port-Of: odoo/enterprise#44956

When search mps by bom, currently we always use "ilike" as operator to search by name. This leads to wrong result when we search by id, bom with the "id" in its name will also be shown. To fix, we don't force to use "ilike". Allow it to change by different cases. Task-3337966 Forward-Port-Of: odoo/enterprise#42547

When search mps by bom, currently we always use "ilike" as operator to search by name. This leads to wrong result when we search by id, bom with the "id" in its name will also be shown.
To fix, we don't force to use "ilike". Allow it to change by different cases.

Task-3337966

Forward-Port-Of: odoo/enterprise#42547

This PR makes the bus service start lazily. Since the bus service start method is no longer async some tests need to adapt the order in which the routes are asserted during tests. community: https://github.com/odoo/odoo/pull/129312 Forward-Port-Of: odoo/enterprise#44730

This PR makes the bus service start lazily. Since the bus service start method is no longer async some tests need to adapt the order in which the routes are asserted during tests.

community: https://github.com/odoo/odoo/pull/129312

Forward-Port-Of: odoo/enterprise#44730

Currently, the "Add a note" span is hidden from HTML view with a t-att-style. Receivers of the follow up report who view their emails in plain text will still see the "Add a note" line. The new change using t-if will properly hide the span for users that view the email in plain text. opw-3413962 Forward-Port-Of: odoo/enterprise#44994 Forward-Port-Of: odoo/enterprise#44657

Currently, the "Add a note" span is hidden from HTML view with a t-att-style. Receivers of the follow up report who view their emails in plain text will still see the "Add a note" line. The new change using t-if will properly hide the span for users that view the email in plain text.

opw-3413962

Forward-Port-Of: odoo/enterprise#44994
Forward-Port-Of: odoo/enterprise#44657

Currently the default deferral amount computation is set to be based on days. Because mostly people want to calculate equal amounts per month, we change the default calculation to that. [task-3441004](https://www.odoo.com/web#id=3441004&menu_id=4720&cids=1&action=333&active_id=967&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#44913

Currently the default deferral amount computation is set to be based on days. Because mostly people want to calculate equal amounts per month, we change the default calculation to that.

[task-3441004](https://www.odoo.com/web#id=3441004&menu_id=4720&cids=1&action=333&active_id=967&model=project.task&view_type=form)

Forward-Port-Of: odoo/enterprise#44913

The styling of the ellipsis clone button was not applied correctly. On clicking on the clone button, there is now a notification telling the user that the text was copied and it closes the popover. Forward-Port-Of: odoo/enterprise#44845

The styling of the ellipsis clone button was not applied correctly.

On clicking on the clone button, there is now a notification telling the user that the text was copied and it closes the popover.

Forward-Port-Of: odoo/enterprise#44845

7cd0563b762569484da1bef7af4ca84e189feca5: There were still old, hardcoded, colors being used in the sign module's PDF viewer. These have been replaced with the new ones, but Sign uses an iframe to render the PDF viewer and the variables weren't being applied. Some of the bootstrap classes, such as `.btn-primary` (changed to `.btn-secondary`), were already on some elements but were also not being applied. A copy of the current CSS variables was needed in the `iframe.scss` file in order t

7cd0563b762569484da1bef7af4ca84e189feca5:
There were still old, hardcoded, colors being used in the sign module's
PDF viewer.
These have been replaced with the new ones, but Sign uses an
iframe to render the PDF viewer and the variables weren't being applied.
Some of the bootstrap classes, such as `.btn-primary` (changed to
`.btn-secondary`), were already on some elements but were also not being
applied.
A copy of the current CSS variables was needed in the `iframe.scss` file
in order to fix these issues.

This also allows us to correct some of the viewer's color issues, which
we override in this same file.

Inputs with the class `o_input` just above the iframe weren't rendering 
well as they were white instead of being the same as the parent's 
background color. To solve this issue we override the value of the CSS 
variable being used by `.o_input`.

fd29f9e8c9b9e225ec0955a54047bff86a5351c5:
The PDF viewer used to be black. As it is now white, and the custom
rotateCw arrow that is injected is a white `.png` image, it is no longer
visible on the white background. There is also a sizing issue.
The fix was to revert to the original rotateCw icon located in the PDF
viewer and use the same way of working as for the other
buttons. To do this a simple ID was needed on the element.



task-3326565
part of task-3326263

Forward-Port-Of: odoo/enterprise#44577
Forward-Port-Of: odoo/enterprise#41035

When having a cash rounding line on an invoice, base amount is taken twice into account in the tax report when grouping by account > tax or tax > account. Steps: - Activate cash rounding, and create one with 0.05 rounding, method 'HALF_UP' and 'biggest_tax' strategy - Create an invoice with a product line with unit price 1.24$, tax 15% (included in price) - Select the rounding method created above. - A rounding line for tax 15.0% and 0.02$ should have been created - Go to tax report an

When having a cash rounding line on an invoice,
base amount is taken twice into account in the tax
report when grouping by account > tax or tax > account.

Steps:

- Activate cash rounding, and create one with
  0.05 rounding, method 'HALF_UP' and
  'biggest_tax' strategy
- Create an invoice with a product line with
  unit price 1.24$, tax 15% (included in price)
- Select the rounding method created above.
- A rounding line for tax 15.0% and 0.02$ should
  have been created
- Go to tax report and group by Account->Tax or
  Tax->Account
-> Base amount is 2.48 instead of 1.24

opw-3336398

Forward-Port-Of: odoo/enterprise#44747
Forward-Port-Of: odoo/enterprise#44324

When the user will add the property, the property field values and Add a Property button are not well aligned with the property labels. Because in this commit https://github.com/odoo/enterprise/commit/22ce8a389ac0a1e03b32077a20caff88fb1ebe39, padding was applied only in property labels. Technical: Adding margin to the labels and padding to the values and Add a Property button. Now labels, values and Add a property button all are well aligned. **Task**-3381693 Forward-Port-Of: odoo/ent

When the user will add the property, the property field values and Add a
Property button are not well aligned with the property labels. Because in this
commit https://github.com/odoo/enterprise/commit/22ce8a389ac0a1e03b32077a20caff88fb1ebe39, padding was applied only in property labels.

Technical:
Adding margin to the labels and padding to the values and Add a Property button.
Now labels, values and Add a property button all are well aligned.

**Task**-3381693

Forward-Port-Of: odoo/enterprise#43227

This commit brings back the style of icons related to the fields available in the sidebar. During the refactor of the report editor, a lot of files present in the legacy folder were removed, and this scss was not yet ported to current stylesheets. With this fix, the mixin has been renamed to match the naming of the other ones, and the style related to the icons has been preserved to the studio_sidebar.scss file. task-3444791 Forward-Port-Of: odoo/enterprise#44837

This commit brings back the style of icons related to the fields available in the sidebar. During the refactor of the report editor, a lot of files present in the legacy folder were removed, and this scss was not yet ported to current stylesheets.

With this fix, the mixin has been renamed to match the naming of the other ones, and the style related to the icons has been preserved to the studio_sidebar.scss file.

task-3444791

Forward-Port-Of: odoo/enterprise#44837

Steps: - Install planning app without demo data. - Try to split shift of sample data. Cause: - The split shift feature was attempting to split shifts of sample data. Fix: - Modified the visibility of the scissor icon so that it only appears when there are actual shifts to split. Forward-Port-Of: odoo/enterprise#44844

Steps:
- Install planning app without demo data.
- Try to split shift of sample data.

Cause:
- The split shift feature was attempting to split shifts of sample data.

Fix:
- Modified the visibility of the scissor icon so that it only appears when there are actual shifts to split.

Forward-Port-Of: odoo/enterprise#44844

Issue: ------ In the report of payroll application (pivot view), payslips (via its payslip lines) which contain no worked day won't be taken into account for the amounts displayed. It is therefore not possible to analyze them. A concrete example are the payslips of the 13th month in the Belgian localization. Cause: ------ To display these amounts, this SQL condition must be met: ```sql SELECT ... CASE WHEN wd.id = min_id.min_line THEN ...(display amount)... ELSE ... END ... FR

Issue:
------
In the report of payroll application (pivot view), payslips (via its payslip lines) which contain no worked day won't be taken into account for the amounts displayed. It is therefore not possible to analyze them.

A concrete example are the payslips of the 13th month in the Belgian localization.

Cause:
------
To display these amounts, this SQL condition must be met:
```sql
SELECT
	...
	CASE WHEN wd.id = min_id.min_line THEN ...(display amount)... ELSE ... END
	...
FROM
	...
	left join hr_payslip_worked_days wd on (wd.payslip_id = p.id)
	...
	left join (select payslip_id, min(id) as min_line from hr_payslip_worked_days group by payslip_id) min_id on (min_id.payslip_id = p.id)
	...
```
Payslips that do not have a working day won't be listed in the `hr_payslip_worked_days` table, so for these payslips we have: `wd.id = NULL` and `min_id.min_line = NULL`.

In postgresql, the condition `NULL = NULL` is not true but unknown.

Solution:
---------
Modify the condition to handle the `NULL` value comparison like this:
`wd.id = min_id.min_line OR (wd.id IS NULL AND min_id.min_line IS NULL)`
This condition can be simplified as PostgreSQL supports `is not distinct from` operator:
`wd.id IS NOT DISTINCT FROM min_id.min_line`

opw-3429153

Forward-Port-Of: odoo/enterprise#44731

Forward-Port-Of: odoo/enterprise#44819 Forward-Port-Of: odoo/enterprise#44766

Forward-Port-Of: odoo/enterprise#44819
Forward-Port-Of: odoo/enterprise#44766

Bugfix. When sending an invoice to SUNAT, if the CDR is already registered on the server, SUNAT will respond with a 500 Server Error. The response content indicates that the invoice was already registered with other data. At the moment, we bail out as soon as we see the 500 Server Error, meaning that we don't check the response content and don't try to retrieve the CDR from the server even though that would be appropriate. With this commit, if we get a 500 Server Error, we still try to dec

Bugfix. When sending an invoice to SUNAT, if the CDR is already registered on the server, SUNAT will respond with a 500 Server Error. The response content indicates that the invoice was already registered with other data.

At the moment, we bail out as soon as we see the 500 Server Error, meaning that we don't check the response content and don't try to retrieve the CDR from the server even though that would be appropriate.

With this commit, if we get a 500 Server Error, we still try to decode the response content.

Forward-Port-Of: odoo/enterprise#44489

In salary configurator some advantages may have requested documents. When the advantage is selected, the requested documents are shown and required, while when the advantage is not selected, the requested documents are hidden. Problem: On start, the requested documents of non-selected advantages are still showing. After this commit they will be hidden. task-3444804 Forward-Port-Of: odoo/enterprise#44849

In salary configurator some advantages may have requested documents. When the advantage is selected, the requested documents are shown and required, while when the advantage is not selected, the requested documents are hidden.

Problem:
On start, the requested documents of non-selected advantages are still showing.

After this commit they will be hidden.

task-3444804

Forward-Port-Of: odoo/enterprise#44849

Steps to reproduce: - Install CRM, Helpdesk. - Go to Settings > Discuss > Check `Custom Email Servers`, Alias Domain = `@example.com`. - CRM > Config > Sales teams > New > Enter Name = Team1 > Save. - Helpdesk > Create a new customer and record some tickets for them, or use an existing customer (e.g., Azure Interior). - CRM > Pipeline > New > Enter Contact = Azure Interior > Edit. - In the Extra Information tab, set Sales Team = Team1 > Save. - From the opportunity view, open the Azur

Steps to reproduce:

- Install CRM, Helpdesk.
- Go to Settings > Discuss > Check `Custom Email Servers`, Alias Domain = `@example.com`.
- CRM > Config > Sales teams > New > Enter Name = Team1 > Save.
- Helpdesk > Create a new customer and record some tickets for them, or use an existing customer (e.g., Azure Interior).
- CRM > Pipeline > New > Enter Contact = Azure Interior > Edit.
	- In the Extra Information tab, set Sales Team = Team1 > Save.
	- From the opportunity view, open the Azure Interior record through the internal link.
- From the customer's profile, click on the Tickets stat button.

Issue:

Traceback: `Record does not exist or has been deleted.` This error occurs because the sales team of the opportunity is passed in the context as `default_team_id`. When clicking the stat button, we search for a helpdesk team using the same context variable, `default_team_id`. Since there is no helpdesk team with that id, the traceback appears.

Solution:

When clicking on the tickets stat button, our aim is to display all helpdesk tickets related to that customer, and the helpdesk team is not relevant in this context. Therefore, we can set `default_team_id` to False before displaying the tickets, and this change will not affect the results.

opw-3371767

Forward-Port-Of: odoo/enterprise#44208

We added the feature to send the Tax Report to the Dutch government for our Dutch clients. This new module (which will be merged into l10n_nl_intrastat in master in a new task) will allow to send the Intra-Communautaire prestaties report (EC Sales List) the same way. Task : 3187020 Forward-Port-Of: odoo/enterprise#44709 Forward-Port-Of: odoo/enterprise#42849

We added the feature to send the Tax Report to the Dutch government for our Dutch clients. This new module (which will be merged into l10n_nl_intrastat in master in a new task) will allow to send the Intra-Communautaire prestaties report (EC Sales List) the same way.

Task : 3187020

Forward-Port-Of: odoo/enterprise#44709
Forward-Port-Of: odoo/enterprise#42849

There was a traceback when right clicking on a spreaded cell beacause of the list "see record" context menu item. Fixed it. Task: [3425493](https://www.odoo.com/web#id=3425493&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form) Forward-Port-Of: odoo/enterprise#44141

There was a traceback when right clicking on a spreaded cell beacause of the list "see record" context menu item. Fixed it.

Task: [3425493](https://www.odoo.com/web#id=3425493&cids=1&menu_id=4720&action=333&active_id=2328&model=project.task&view_type=form)

Forward-Port-Of: odoo/enterprise#44141