Saturday, April 6, 2024
4 changes · saas-17.1
Miscellaneous changes
This pr will add an id on a div to be able to do a xpath on it. task: 3756179 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157648
Original PR description
This pr will add an id on a div to be able to do a xpath on it. task: 3756179 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157648
First commit fixes an issue introduced by https://github.com/odoo/odoo/pull/154203 which could keep the autocomplete options list opened even after a click away when the user would "drag and drop" an option out of the list instead of simply clicking on it. This is caused by the fact that the onInputBlur code is directly terminated in this case (because of ignoreBlur) while it is the only way for the autocomplete list to be closed in this case. The solution is therefore to add an external listene
Original PR description
First commit fixes an issue introduced by https://github.com/odoo/odoo/pull/154203 which could keep the autocomplete options list opened even after a click away when the user would "drag and drop" an…
First commit fixes an issue introduced by https://github.com/odoo/odoo/pull/154203 which could keep the autocomplete options list opened even after a click away when the user would "drag and drop" an option out of the list instead of simply clicking on it. This is caused by the fact that the onInputBlur code is directly terminated in this case (because of ignoreBlur) while it is the only way for the autocomplete list to be closed in this case. The solution is therefore to add an external listener on pointer down which will always close the autocomplete list when clicking away from it. Steps to reproduce: - go to any autocomplete (crm salesperson for example) - click on the input - drag and drop a result outside of the list - try to close the autocomplete list by clicking away Before the fix, the autocomplete list would only close by scrolling or clicking on the input once again. Second commit fixes an issue regarding unwanted interaction between the regular autocomplete option click selection and the onChange handler from the input field hook used in the PartnerAutoCompleteCharField component. This became an issue starting from https://github.com/odoo/odoo/pull/154203 because of the disappearance of the t-on-mousedown.prevent handler placed on the autocomplete options list which would prevent the onChange event from being triggered when clicking on an option. The issue would be that the onChange handler from the input field hook would take precedence over the option click handler of the autocomplete which would most of the time be ignored afterwards. The solution found for this problem is to prevent the immediate propagation of the change event in the autocomplete handler when an option has been clicked on so that it will never be propagated to the input field hook handler in this case. Steps to reproduce: - Go to contacts and open a company contact - Type in the name field a few characters (at least 3) - Click on any autocomplete option Most of the time, the option will not be applied and the name won't change Forward-Port-Of: odoo/odoo#159765 Forward-Port-Of: odoo/odoo#159333
In this https://github.com/odoo/enterprise/commit/76caf5f5675f97128b88fbcffedaf1e85da516d5, it was decided to remove the report. But we received a lot of feedbacks about users missing the report, especially from anglo-saxon countries, where this report is often used in Audit processes to report on the differences between the Accounting and Bank reported amounts on bank accounts. In this pr we decided to put it back and improve it. What has been improved: - The display of the report is now co
Original PR description
In this https://github.com/odoo/enterprise/commit/76caf5f5675f97128b88fbcffedaf1e85da516d5, it was decided to remove the report. But we received a lot of feedbacks about users missing the report, especially from anglo-saxon countries, where this report is often used in Audit processes to report on the differences between the Accounting and Bank reported amounts on bank accounts. In this pr we decided to put it back and improve it. What has been improved: - The display of the report is now consistent with the different reports - Use of custom engine - New sections added - Rework of the warnings task: 3756179 Forward-Port-Of: odoo/enterprise#58640
**Steps to reproduce:** 1- Navigate to Inventory > Configuration > Warehouses and select the warehouse 2- Click on the Routes smart button and filter by archived routes 3- Unarchive the Replenish on Order (MTO) route 4- Navigate to Sales > Products > Products and create a new product 5- Make the product a Recurring product that has the product type set to storable and the invoicing policy set to ordered quantities 6- Navigate to the Inventory tab and enable the Replenish on Order (MT
Original PR description
**Steps to reproduce:** 1- Navigate to Inventory > Configuration > Warehouses and select the warehouse 2- Click on the Routes smart button and filter by archived routes 3- Unarchive the Replenish on…
**Steps to reproduce:** 1- Navigate to Inventory > Configuration > Warehouses and select the warehouse 2- Click on the Routes smart button and filter by archived routes 3- Unarchive the Replenish on Order (MTO) route 4- Navigate to Sales > Products > Products and create a new product 5- Make the product a Recurring product that has the product type set to storable and the invoicing policy set to ordered quantities 6- Navigate to the Inventory tab and enable the Replenish on Order (MTO) and Manufacture Routes 7- Navigate to Sales and create a new quote and confirm it with the newly created product 8- Click on Create Invoice and then Create Draft Invoice 9- Click on Confirm **Current behavior before PR:** This is happening because while creating the draft invoice we pass the default move type for the invoice in the context and because the attribute 'move_type' has the same name in 'account.move' and 'procurement.group' so when getting the default value to create the procurement group it gets the value in the context which is for the account move so this value is incorrect for the move_type in procurement group **Desired behavior after PR is merged:** We clean the context that was stored for creating the invoice before posting it as this context will not be used anymore opw-3718420 Forward-Port-Of: odoo/enterprise#60118 Forward-Port-Of: odoo/enterprise#59164