Tuesday, August 9, 2022
12 changes · master
New functionality added to Odoo
Knowledge articles can now include an automatically updated table of contents based on the page headings. Users can click a section in the table to jump directly to that part of the article, making longer content easier to navigate in both editing and public views.
Original PR description
Purpose ======== Allow users to create a table of contents dynamically listing all headers in the page. When clicking on a section name, the page will scroll (both in back end and front end view) to the selected heather and highlight it for a brief interval of time. Task-2818474 Co-authored-by: Aurélien Warnon <awa@odoo.com> Co-authored-by: julien-banken <jbn@odoo.com> Co-authored-by: abd-msyukyu-odoo <abd@odoo.com> Co-authored-by: fbarbe00 <faba@odoo.com>
Enhancements to existing features
Resolved issues and error corrections
Fixed an issue that could cause an error when opening a product after a recent quality control change. The quality check count now works correctly for multiple products, keeping product pages accessible for users.
Original PR description
Since https://github.com/odoo/enterprise/pull/27602 a traceback appears when clicking on a product. This comes from the calculation of the number of quality checks, where the domain wrongly assumed there would be only one id in self.
Miscellaneous changes
This draft change touches the Argentina electronic invoicing localization manifest. Based on the available details, it appears to be a small metadata or configuration update with limited business impact.
Unnecessary or overly technical help messages were removed or moved out of the user interface across many Odoo modules. This reduces translation effort, makes screens less cluttered, and keeps tooltips focused on information that is genuinely useful to users.
Original PR description
This commit aims at removing unuseful help message to: 1/ reduce translators work, to focus on more useful translations 2/ not sending unuseful information in load_views 3/ reduce help message to useful messages, as we mark fields having a tooltip The main use cases: - REMOVED: help redundant with the field name, providing no extra info - MOVED TO COMMENT: technical help messages, that should not be in UX
This change moves delivered price fields into the core field service sales module so they are available whenever needed. It prevents errors when signing reports if the reporting add-on is not installed first, making the workflow more reliable for users.
Original PR description
Before this commit: - delivered_price_subtotal, delivered_price_tax and delivered_price_total fields are added in industry_fsm_sale_report but used in industry_fsm_sale. An error occured when trying to sign report as industry_fsm_sale can be installed before installing industry_fsm_sale_report. After this commit: - delivered_price_subtotal, delivered_price_tax and delivered_price_total and delivered_price_subtotal, delivered_price_tax and delivered_price_total moved to sale_order_line.py in industry_fsm_sale. Task-2892346
Steps to reproduce: - Install `Documents` and `Dashboard` modules - Go to Documents > Select documents > Add to the dashboard - Go to Dashboard Issue: Traceback raised. Cause: Trying to check if there is some tags by doing tags.length while there are none. `tags` is null in this case because there is no searchModel for document view in the Dashboard. Solution: Return an empty list if no tags available in searchModel. opw-2946602 Forward-Port-Of: odo
Original PR description
Steps to reproduce:
- Install `Documents` and `Dashboard` modules
- Go to Documents > Select documents > Add to the dashboard
- Go to Dashboard
Issue:
Traceback raised.
Cause:
Trying to check if there is some tags by doing tags.length while there
are none. `tags` is null in this case because there is no searchModel
for document view in the Dashboard.
Solution:
Return an empty list if no tags available in searchModel.
opw-2946602
Forward-Port-Of: odoo/enterprise#30210Steps to reproduce: 1) config - a client with a certain fiscal position - a tax with tax included - at a certain rate e.g. 21% - another tax with the same rate, but tax excl., with field 'Base affected by previous taxes' ticked - on the fiscal position set on the client, a tax mapping from that 1st tax to that 2nd one - a rental product on which the 1st tax - the one tax incl. - is applied 2) flow - create a rental order - select the rental product (the wizard will open) - add 1 unit
Original PR description
Steps to reproduce: 1) config - a client with a certain fiscal position - a tax with tax included - at a certain rate e.g. 21% - another tax with the same rate, but tax excl., with field 'Base…
Steps to reproduce: 1) config - a client with a certain fiscal position - a tax with tax included - at a certain rate e.g. 21% - another tax with the same rate, but tax excl., with field 'Base affected by previous taxes' ticked - on the fiscal position set on the client, a tax mapping from that 1st tax to that 2nd one - a rental product on which the 1st tax - the one tax incl. - is applied 2) flow - create a rental order - select the rental product (the wizard will open) - add 1 unit - edit the line - click on the calendar (the wizard will open) Issue: The unit_price is not tax included Cause: When the rental order is not saved, fetching the tax from the first initialised line is not possible. Therefore `product_taxes_after_fp = product_taxes` and the unit_price will be equal to its lst_price. https://github.com/odoo/enterprise/blob/0359eff3ffacc62a0de6e5bbb0c8b144b8d2e781/sale_renting/wizard/rental_configurator.py#L104-L118 Solution: When editing the line, give the `default_tax_ids` to the `_openRentalConfigurator`. Consequently, `unit_price` will be computed with the correct fpos. opw-2893564 Forward-Port-Of: odoo/enterprise#29536
Since product.avatax.category.csv was created new categories were added on Avatax's side. This diff is large because the original file wasn't sorted. This commit sorts the file so future diffs are smaller. No codes were removed. If this becomes a frequent issue we can consider doing this in `avatax_sync_company_params()` so the user can trigger updates by querying the API whenever they want. opw-2945059 PR note: a cleaned up diff is [here](https://gist.github.com/jorenvo/94e05
Original PR description
Since product.avatax.category.csv was created new categories were added on Avatax's side. This diff is large because the original file wasn't sorted. This commit sorts the file so future diffs are smaller. No codes were removed. If this becomes a frequent issue we can consider doing this in `avatax_sync_company_params()` so the user can trigger updates by querying the API whenever they want. opw-2945059 PR note: a cleaned up diff is [here](https://gist.github.com/jorenvo/94e05fb08b4b80824e7cb78f2ed226d4). Forward-Port-Of: odoo/enterprise#30220
Before this commit, the recurring prices were only available from the product template form view. taskid: 2886054 Forward-Port-Of: odoo/enterprise#30043 Forward-Port-Of: odoo/enterprise#29633
Original PR description
Before this commit, the recurring prices were only available from the product template form view. taskid: 2886054 Forward-Port-Of: odoo/enterprise#30043 Forward-Port-Of: odoo/enterprise#29633
The PE government requires all deliveries to have a GuiaRemision XML document sent to the SUNAT / OSE for signing. This module enables the feature to generate and send a XML for GuiaRemision, and the ability to print these details on the Delivery Slip PDF. Legal ref: Version Control 23/03/2022: https://cpe.sunat.gob.pe/sites/default/files/inline-files/AjustesValidacionesCPEv20220323_1.xlsx Website: https://cpe.sunat.gob.pe/tipos_de_comprobantes/guiaderemision Document with the struc
Original PR description
The PE government requires all deliveries to have a GuiaRemision XML document sent to the SUNAT / OSE for signing. This module enables the feature to generate and send a XML for GuiaRemision, and the ability to print these details on the Delivery Slip PDF. Legal ref: Version Control 23/03/2022: https://cpe.sunat.gob.pe/sites/default/files/inline-files/AjustesValidacionesCPEv20220323_1.xlsx Website: https://cpe.sunat.gob.pe/tipos_de_comprobantes/guiaderemision Document with the structure of the XML: https://cpe.sunat.gob.pe/sites/default/files/inline-files/Guia_GUIA_REMISION_REMITENTE.pdf -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/enterprise#30161 Forward-Port-Of: odoo/enterprise#23158
- Add translations for fr and de task-2928312 Forward-Port-Of: odoo/enterprise#30184 Forward-Port-Of: odoo/enterprise#29625
Original PR description
- Add translations for fr and de task-2928312 Forward-Port-Of: odoo/enterprise#30184 Forward-Port-Of: odoo/enterprise#29625
There was no check that the partner selected was belonging to the same company than the current `account.move`. Ticket #2881230 Forward-Port-Of: odoo/enterprise#30041 Forward-Port-Of: odoo/enterprise#29515
Original PR description
There was no check that the partner selected was belonging to the same company than the current `account.move`. Ticket #2881230 Forward-Port-Of: odoo/enterprise#30041 Forward-Port-Of: odoo/enterprise#29515