Monday, February 13, 2023
10 changes · master
Enhancements to existing features
This update removes leftover internal code from the Social app after a previous cleanup. It has no expected change for users, but helps keep the system simpler and easier to maintain.
Original PR description
Small oversight of 0ae0dd6cb5b0a82cb8c53b859fbb6fd6b22c0072 Where we removed OWL directives but forgot to remove the "renderingContext" override in the social views. Task-3184739
Invoice chatter messages are now clearer when expected payment dates change, especially for invoices split into multiple installments by payment terms. This helps users better understand which payment timing changed and keeps these messages limited to invoices.
Original PR description
This commit updates the message that gets posted in the chatter when the expected payment date changes to make it clearer, especially when there are several installments on the invoice because of the payment terms. The message is only to be posted on invoices. task-3137957
The Chilean reporting localization now uses English as the source language, with Spanish provided through translations. This improves consistency with Odoo localization standards and makes future maintenance and translation updates easier.
Original PR description
Before this PR, all this localisation was written in Spanish, but all the localisation have to be written in english and then translated back in the native language. This PR correct that. Task-id: 3166093
Miscellaneous changes
Steps to reproduce: - install l10n_be_reports - accounting -> Reporting -> Tax Report - click Save, and try to select XML to print it -> get traceback. Bug: `_get_attachments_to_save` expects the print function to be in the `account.report` module https://github.com/odoo/enterprise/blob/16.0/account_reports/wizard/report_export_wizard.py#L63 also https://github.com/odoo/enterprise/blob/16.0/l10n_be_reports/wizard/report_export_wizard.py#L16 Fix: move `print_tax_report_to_xm
Original PR description
Steps to reproduce: - install l10n_be_reports - accounting -> Reporting -> Tax Report - click Save, and try to select XML to print it -> get traceback. Bug: `_get_attachments_to_save` expects the print function to be in the `account.report` module https://github.com/odoo/enterprise/blob/16.0/account_reports/wizard/report_export_wizard.py#L63 also https://github.com/odoo/enterprise/blob/16.0/l10n_be_reports/wizard/report_export_wizard.py#L16 Fix: move `print_tax_report_to_xml` to `account.report` OPW-3144787 Forward-Port-Of: odoo/enterprise#36627
Now that inheritance is correctly called some additional queries are added in posting process, as groups are correctly computed and customers correctly fetched. Task-3175768 (Mail: check inheritances / overrides) Forward-Port-Of: odoo/enterprise#37021
Original PR description
Now that inheritance is correctly called some additional queries are added in posting process, as groups are correctly computed and customers correctly fetched. Task-3175768 (Mail: check inheritances / overrides) Forward-Port-Of: odoo/enterprise#37021
This commit fixes the issue that occured when the export option was selected from the control panel actions. Since wrong props were given to the ExportDataDialog component, it crashed instantly. Now, the dialog opens correctly and let the user select and export the appropriate elements. Community PR introducing defaultProps and props in the ExportDataDialog : https://github.com/odoo/odoo/pull/112381 Forward-Port-Of: odoo/enterprise#36933
Original PR description
This commit fixes the issue that occured when the export option was selected from the control panel actions. Since wrong props were given to the ExportDataDialog component, it crashed instantly. Now, the dialog opens correctly and let the user select and export the appropriate elements. Community PR introducing defaultProps and props in the ExportDataDialog : https://github.com/odoo/odoo/pull/112381 Forward-Port-Of: odoo/enterprise#36933
Forward-Port-Of: odoo/enterprise#37002
Original PR description
Forward-Port-Of: odoo/enterprise#37002
The validation of the documents was always sent to the OCR, even when the OCR wasn't actually used on the document. Forward-Port-Of: odoo/enterprise#36993 Forward-Port-Of: odoo/enterprise#36809
Original PR description
The validation of the documents was always sent to the OCR, even when the OCR wasn't actually used on the document. Forward-Port-Of: odoo/enterprise#36993 Forward-Port-Of: odoo/enterprise#36809
Before this commit, when synchronizing an order with a discount (either a Promotion Discount or a Shipping Discount), the Amazon connector would take the value Amazon sent without considering if the amount was tax included or not, and pass it as is without knowing if it should be tax included or not, which could lead to some sales order lines having a wrong discount percentage. The Amazon connector will now take this info from Amazon and recompute it in order to match the expected value. t
Original PR description
Before this commit, when synchronizing an order with a discount (either a Promotion Discount or a Shipping Discount), the Amazon connector would take the value Amazon sent without considering if the amount was tax included or not, and pass it as is without knowing if it should be tax included or not, which could lead to some sales order lines having a wrong discount percentage. The Amazon connector will now take this info from Amazon and recompute it in order to match the expected value. task-2700405 opw-3116517 Forward-Port-Of: odoo/enterprise#36754 Forward-Port-Of: odoo/enterprise#36049
This PR change the implementation of the sale_subscription_dashboard KPIs view to batch the retrieval of information. Before this PR, each point coordinate of the several KPI dashboard graph were computed with a sql request. As each graph would draw a point per day, the amount of SQL request to display the dashboard was overly high (~30 per graphs).  Production database wit
Original PR description
This PR change the implementation of the sale_subscription_dashboard KPIs view to batch the retrieval of information. Before this PR, each point coordinate of the several KPI dashboard graph were…
This PR change the implementation of the sale_subscription_dashboard KPIs view to batch the retrieval of information. Before this PR, each point coordinate of the several KPI dashboard graph were computed with a sql request. As each graph would draw a point per day, the amount of SQL request to display the dashboard was overly high (~30 per graphs).  Production database with a lot of account move lines and subscription could not be displayed without a time out error. The KPI dashboard is displaying 9 graphs and the amount of SQL requests is now approximately divided by 30. Moreover, the PR allows the function to work with a defined set of dates instead of a start_date and end_date. Furthermore, some indexes are added on account_move_lines subscription_start_date and subscription_end_date and company_id to speed up graph generation. As a result, the PR provides significant speed-up for the KPI view, especially for large database. The specification of the KPI API has also been updated to reflect these changes and now return an array tuple containing the date and value of each data point. task-id : 3061203 Forward-Port-Of: odoo/enterprise#36879 Forward-Port-Of: odoo/enterprise#35792