Daily updates from Odoo
Thursday, July 20, 2023
11 changes · master
Enhancements to existing features
Accounting reporting was adjusted to work with a newer underlying system interface, helping keep report generation compatible and reliable. A related Studio update improves how custom record identifiers are inserted, supporting smoother configuration management.
Original PR description
Linked to odoo/odoo#129029
The live chat helpdesk mail shortcut setup has been moved to the mail area so it can be managed in the more appropriate shared location. This is an internal organization improvement that should make future maintenance easier without changing day-to-day user workflows.
Original PR description
community: https://github.com/odoo/odoo/pull/128120
Resolved issues and error corrections
This update fixes an issue in Appointments where the leave management wizard referred to an outdated date field, which could prevent the date selector from working correctly. It also reorganizes and renames Appointment menus so users see clearer, more consistent navigation.
Original PR description
The leave wizard was using an older field name for its date widget. The menus for appointment were not ordered properly. And the name of the menus did not match the name of the actions. task-3434098
Removing a tax during bank reconciliation now correctly removes the leftover empty journal entry line. This prevents confusing or inaccurate accounting entries from remaining after users adjust manual operations.
Original PR description
To replicate: - Open the bank reconciliation widget - Choose a statement line (preferably a line with no partner) - Mount the suspense line, to open the Manual Operations tab - Add a tax - Remove the tax You will notice the original base line has no debit/credit/balance but it stays in the journal entry (line_ids). No bug report (found by myself when adding the vehicle to the bank rec widget)
Features or functions removed from Odoo
VoIP now relies on the existing phone validation process for phone and mobile numbers instead of keeping duplicate sanitized fields. This reduces redundant data handling and helps keep contact and call information consistent with less maintenance overhead.
Original PR description
Since phone numbers in `phone` and `mobile` fields are already sanitized by the phone_validation module, there is no need to have the `sanitized_phone` and `sanitized_mobile` fields. Part of task-2832241 Upgrade: odoo/upgrade#3530
Miscellaneous changes
The `_compute_car_id` method would search for any vehicle linked to the employee, but without taking care of the vehicle type. Forward-Port-Of: odoo/enterprise#44200
Original PR description
The `_compute_car_id` method would search for any vehicle linked to the employee, but without taking care of the vehicle type. Forward-Port-Of: odoo/enterprise#44200
To avoid having articles with long names, we will remove the prefixes 'Kanban of' and 'List of' from the names and the first H1 headings of the articles created via the wysiwyg helper of Knowledge. This modification will make the articles appear lighter and less redundant. task-3384707 Forward-Port-Of: odoo/enterprise#43285
Original PR description
To avoid having articles with long names, we will remove the prefixes 'Kanban of' and 'List of' from the names and the first H1 headings of the articles created via the wysiwyg helper of Knowledge. This modification will make the articles appear lighter and less redundant. task-3384707 Forward-Port-Of: odoo/enterprise#43285
A small oversight in https://github.com/odoo/enterprise/pull/37891 introduced faulty translations with a different amount of "%s" items compared to the strings in the source code. This leads to TypeErrors: File "...l10n_cl_edi/models/account_move.py", line 480, in _l10n_cl_action_response msg = _('Document %s failed with the following response:') % (action_response[status_type].description) + \ TypeError: not all arguments converted during string formatting This commit fixes those
Original PR description
A small oversight in https://github.com/odoo/enterprise/pull/37891 introduced faulty translations with a different amount of "%s" items compared to the strings in the source code. This leads to…
A small oversight in https://github.com/odoo/enterprise/pull/37891 introduced faulty translations with a different amount of "%s" items compared to the strings in the source code. This leads to TypeErrors:
File "...l10n_cl_edi/models/account_move.py", line 480, in _l10n_cl_action_response
msg = _('Document %s failed with the following response:') % (action_response[status_type].description) + \
TypeError: not all arguments converted during string formatting
This commit fixes those faulty translations. Strings prepended with #| were not updated because those refer to "Previously untranslated" strings [1].
To fix the problem in affected databases the l10n_cl_edi module needs to be updated or the Spanish translations must be updated via the technical settings.
Spanish translations provided by VBE.
opw-3415429
Co-authored-by: Valentino Bedetta <vbe@odoo.com>
[1] https://www.gnu.org/software/gettext/manual/html_node/PO-Files.html
Forward-Port-Of: odoo/enterprise#44091Set up currency rates of day A and day B Set Solucion Factible PAC Create an invoice in USD with date A Create a payment complement with date B -> CFDI validate correctly Set Quadrum PAC Create another invoice in USD with date A Create a payment complement with date B -> CFDI error Código: CRP20274 Mensaje: El campo ImporteP que corresponde a Traslado, no es igual a la suma de los importes de los impuestos registrados en el documento relacionado donde el impuesto del documento relaciona
Original PR description
Set up currency rates of day A and day B Set Solucion Factible PAC Create an invoice in USD with date A Create a payment complement with date B -> CFDI validate correctly Set Quadrum PAC Create another invoice in USD with date A Create a payment complement with date B -> CFDI error Código: CRP20274 Mensaje: El campo ImporteP que corresponde a Traslado, no es igual a la suma de los importes de los impuestos registrados en el documento relacionado donde el impuesto del documento relacionado sea igual al campo ImpuestoP de este elemento y la TasaOCuotaP del documento relacionado sea igual al campo TasaOCuotaP de este elemento. Due to a recent change within, Quadrum, the rounding method has been modified https://support.finkok.com/support/solutions/articles/31000170307-ajustes-validaciones-complemento-pagos-2-0 By changing the rounding method to “HALF-UP”, the payment complements are all signed properly opw-3416955 Forward-Port-Of: odoo/enterprise#44222
When expanding the last level of a groupby in any report, it crashed if the related model did not correspond to any caret option key either in the result of the custom handler's _caret_options_initializer() or in _caret_options_initializer_default(). This was due to the fact the controller's caretOptions() getter returned undefined, and LineName's hasCaretOptions() tried to access the 'length' field of its result. Forward-Port-Of: odoo/enterprise#43869
Original PR description
When expanding the last level of a groupby in any report, it crashed if the related model did not correspond to any caret option key either in the result of the custom handler's _caret_options_initializer() or in _caret_options_initializer_default(). This was due to the fact the controller's caretOptions() getter returned undefined, and LineName's hasCaretOptions() tried to access the 'length' field of its result. Forward-Port-Of: odoo/enterprise#43869
Ticket: 63066 Task latam: 1051 **Steps to reproduce**: 1) Go to runbot Odoo 16 enterprise and install "l10n_ar_edi" module (Argentinean Electronic Invoicing) and then "l10n_ar_reports" (Argentinean Accounting Reports). 2) Take position on Argentinian company (AR) (Responsable Inscripto) . 3) Go to Accounting / Reporting / Statement Reports / Tax Report and click on button "XLSX". 4) Select moves from current month. **Current behavior**: Date format on XLSX report is incorre
Original PR description
Ticket: 63066 Task latam: 1051 **Steps to reproduce**: 1) Go to runbot Odoo 16 enterprise and install "l10n_ar_edi" module (Argentinean Electronic Invoicing) and then "l10n_ar_reports" (Argentinean Accounting Reports). 2) Take position on Argentinian company (AR) (Responsable Inscripto) . 3) Go to Accounting / Reporting / Statement Reports / Tax Report and click on button "XLSX". 4) Select moves from current month. **Current behavior**: Date format on XLSX report is incorrect (date column).  **Expected behavior**: Date format on XLSX report is correct (date column).  **Video**: https://drive.google.com/file/d/1ECNCET76PPpSVyxtBKrUZrsZhnSgZ66k/view Forward-Port-Of: odoo/enterprise#43690