Odoo Changelog — 2025-01-02

Thursday, January 2, 2025

4 changes · 17.0

Bug Fixes(4)

Resolved issues and error corrections

[FW][IMP] l10n_mx_edi: Non-deterministic elements in views

Enterprise17.0l10n_mx_edi

This update addresses a technical issue in the l10n_mx_edi module that caused reports to break when views were inherited. By adding names to specific view elements, the change ensures these views remain stable even with small updates, preventing disruptions to report generation. This improves the reliability of the Mexican EDI functionality.

Original PR description

There are currently some elements in views that are not reachable on a deterministic way when those views are inherited. That means, to reach them, positional selectors need to be used (e.g. `last()`). That causes inherited views to get broken when there are small changes in element position.

A good example of this is [1]:

    <div class="digital-stamp">
        <span>Extra Info</span>
    </div>

Which can't be filtered by:
- Class, because there are several `<div>` elements with the same class
- Text content, because when content is translated, selector will fail

To solve the above, this change provides names for several elements, to make possible/easier to reach them on a safely manner.

[1] https://github.com/odoo/enterprise/blob/d6346ef8/l10n_mx_edi/views/l10n_mx_edi_report_invoice.xml#L123

Forward-Port-Of: odoo/enterprise#64604
Forward-Port-Of: odoo/enterprise#63957

#l10n_mx_edi#reports#stability

[FW][FIX] documents_spreadsheet: Fix template creation with grouped dates

PR #76298

Enterprise17.0documents_spreadsheet

This update resolves an issue where spreadsheet templates couldn't correctly handle grouped date fields. The fix prevents incorrect assumptions about date granularity during template creation, ensuring accurate spreadsheet generation. This improves the reliability of reports and dashboards.

Original PR description

When creating a spreadsheet.template, we ensure the values of each groupbys are correctly ordered. Tthe current implementation assumes that the groupby will return values present in the tables and not values altered by a groupby with specific granularity (namely date fields) by adding the values to the search domain. Unfortunately, the search does not support dates with a granularity different than `day`.
This revision ensures that we do not add such grouped values to the search domain.

Task-4438631

Forward-Port-Of: odoo/enterprise#76290

#reporting#templates#data

[FW][FIX] hr_contract_salary: typo on `message_subscribe` call

PR #76056

Enterprise17.0hr_contract_salary

This update corrects a minor typo in the system's notification process for employee contracts. The fix ensures that salary-related messages are correctly sent, preventing potential disruptions to payroll and contract management workflows. This ensures accurate and timely communication regarding contract details.

Original PR description

Forward-Port-Of: odoo/enterprise#75991

#hr#contracts#notifications

[FW][FIX] helpdesk: fix issue with onboarding tour

PR #76147

Enterprise17.0helpdesk

This update fixes a bug preventing the helpdesk onboarding tour from progressing when users provided input. The fix removed a hardcoded string check, allowing the tour to correctly advance based on user actions, improving the user experience.

Original PR description

Previously, when a customer was selected or input was entered, the onboarding tour failed to proceed to the next step.

With this fix, the tour will correctly advance when the user provides input.


Without demo data, the database does not have Deco.so i so I select
the partner.

When the user does not provide the ticket name 'SAP is bad, paid by Odoo,'
the tour will not move to the next step because we had checked a fixed string.
Therefore, I have removed it and checked the kanban class instead.

task-4372470

Forward-Port-Of: odoo/enterprise#75106

#onboarding#tour#helpdesk

There are currently some elements in views that are not reachable on a deterministic way when those views are inherited. That means, to reach them, positional selectors need to be used (e.g. `last()`). That causes inherited views to get broken when there are small changes in element position. A good example of this is [1]: <div class="digital-stamp"> <span>Extra Info</span> </div> Which can't be filtered by: - Class, because there are several `<div>` elements with the same class - Text content, because when content is translated, selector will fail To solve the above, this change provides names for several elements, to make possible/easier to reach them on a safely manner. [1] https://github.com/odoo/enterprise/blob/d6346ef8/l10n_mx_edi/views/l10n_mx_edi_report_invoice.xml#L123 Forward-Port-Of: odoo/enterprise#64604 Forward-Port-Of: odoo/enterprise#63957

When creating a spreadsheet.template, we ensure the values of each groupbys are correctly ordered. Tthe current implementation assumes that the groupby will return values present in the tables and not values altered by a groupby with specific granularity (namely date fields) by adding the values to the search domain. Unfortunately, the search does not support dates with a granularity different than `day`. This revision ensures that we do not add such grouped values to the search domain. Task-4438631 Forward-Port-Of: odoo/enterprise#76290

Previously, when a customer was selected or input was entered, the onboarding tour failed to proceed to the next step. With this fix, the tour will correctly advance when the user provides input. Without demo data, the database does not have Deco.so i so I select the partner. When the user does not provide the ticket name 'SAP is bad, paid by Odoo,' the tour will not move to the next step because we had checked a fixed string. Therefore, I have removed it and checked the kanban class instead. task-4372470 Forward-Port-Of: odoo/enterprise#75106