Daily updates from Odoo
Saturday, April 27, 2024
6 changes · master
Resolved issues and error corrections
Adds a test to ensure the spreadsheet pivot side panel handles reference-based measures without crashing. This helps protect users editing subscription dashboards from interruptions when opening cell details.
Original PR description
…anel Steps to reproduce the issue on a fresh runbot database: - open the Subscription dashboard in edit mode - Right click on cell "Data!B7" => boom The pivot `#11` measure is `order_reference` which is a Reference field. This type of field had no aggregator specified which crashes the side panel. Note: This commit is only a UI test. See the fix in the community branch. Task: 3869693
Miscellaneous changes
Before, using a column group on the OSS report broke the layout, as each country line displayed more cells than it should, and they hence mismatched the column headers. This was due to bad management of the column groups: when there was more than one column group, the tax_sums variable contained more than one value, and we were then looping on each column for each tax sum to generate the columns of the country line, which was wrong, since options['columns'] already contained the columns of ea
Original PR description
Before, using a column group on the OSS report broke the layout, as each country line displayed more cells than it should, and they hence mismatched the column headers. This was due to bad management of the column groups: when there was more than one column group, the tax_sums variable contained more than one value, and we were then looping on each column for each tax sum to generate the columns of the country line, which was wrong, since options['columns'] already contained the columns of each column group. Forward-Port-Of: odoo/enterprise#61530
Some codes in UNSPSC list were reported as missing, updated missing codes and added them to our list. Task Id: 3871714 Forward-Port-Of: odoo/enterprise#61252
Original PR description
Some codes in UNSPSC list were reported as missing, updated missing codes and added them to our list. Task Id: 3871714 Forward-Port-Of: odoo/enterprise#61252
Case 1: The user can cancel the document directly from the SAT. In that case, in odoo, the user needs to "Request Cancel" first even if the SAT state becomes 'cancelled'. To improve that, this case is now managed by adding a new cancel document automatically on the invoice. Case 2: The user can request a cancellation from the SAT. Currently, the invoice is marked as "cancel" even if the SAT rejects the cancellation. In order to manage that, let's introduce a new document: 'invoice_can
Original PR description
Case 1: The user can cancel the document directly from the SAT. In that case, in odoo, the user needs to "Request Cancel" first even if the SAT state becomes 'cancelled'. To improve that, this case is now managed by adding a new cancel document automatically on the invoice. Case 2: The user can request a cancellation from the SAT. Currently, the invoice is marked as "cancel" even if the SAT rejects the cancellation. In order to manage that, let's introduce a new document: 'invoice_cancel_requested'. Forward-Port-Of: odoo/enterprise#61607 Forward-Port-Of: odoo/enterprise#60905
To Reproduce: ============= - create a service Product with **invoicing policy** based on milestones and **create on Order** a task in fsm - create Sale order with this product and confirm it - a task is created, mark the task as done (with the button 'Mark as Done') -> the delivered quantity of the sale order line is updated to 1 Problem: ======== - marking the task as done should not update the delivered quantity of the sale order line of product based on milestones Solution: ==
Original PR description
To Reproduce: ============= - create a service Product with **invoicing policy** based on milestones and **create on Order** a task in fsm - create Sale order with this product and confirm it - a task is created, mark the task as done (with the button 'Mark as Done') -> the delivered quantity of the sale order line is updated to 1 Problem: ======== - marking the task as done should not update the delivered quantity of the sale order line of product based on milestones Solution: ========= add condition to check if the product invoicing policy is based on milestones before updating the delivered quantity of the sale order line as it will be done when the milestones are reached opw-3850167 Forward-Port-Of: odoo/enterprise#61304
After the changes in the related community PR, Commit [2] is no longer needed as that use case in [2] will also resolved in the community PR mentioned below Community PR:- https://github.com/odoo/odoo/pull/163305 [2] https://github.com/odoo/enterprise/pull/58964/commits/7845ff85cad0714a95866f9bfcc9d717960ecf3c sentry-3954475523 Forward-Port-Of: odoo/enterprise#61444
Original PR description
After the changes in the related community PR, Commit [2] is no longer needed as that use case in [2] will also resolved in the community PR mentioned below Community PR:- https://github.com/odoo/odoo/pull/163305 [2] https://github.com/odoo/enterprise/pull/58964/commits/7845ff85cad0714a95866f9bfcc9d717960ecf3c sentry-3954475523 Forward-Port-Of: odoo/enterprise#61444