Wednesday, December 25, 2024
4 changes · saas-17.2
Miscellaneous changes
Steps to reproduce: ------------- - Install Sales, Field Service, and Stock, - Go into Field service and open any task that has products. - Through stat button on the top access the product catalog. - Click on burger menu on any service type product. Issue: - View Availability option should not be shown for service type products Cause: - No condition to make it invisible. Solution: - Added a condition when product type is service to the option invisible. task-3801551
Original PR description
Steps to reproduce: ------------- - Install Sales, Field Service, and Stock, - Go into Field service and open any task that has products. - Through stat button on the top access the product catalog. - Click on burger menu on any service type product. Issue: - View Availability option should not be shown for service type products Cause: - No condition to make it invisible. Solution: - Added a condition when product type is service to the option invisible. task-3801551 Forward-Port-Of: odoo/enterprise#75757 Forward-Port-Of: odoo/enterprise#58817
Issue introduced at https://github.com/odoo/odoo/commit/ce92dedea0fd3cdc73da6366c20b8052bb04f7e9 , While doing the fix for ewaybill, now it's causing issue for `E-Invoice`, because the partner buyer details were changed from Purchase Document to Move type being a Outbound In this fix we only change Buyer-Seller Details only if it's for e-waybill Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I conf
Original PR description
Issue introduced at https://github.com/odoo/odoo/commit/ce92dedea0fd3cdc73da6366c20b8052bb04f7e9 , While doing the fix for ewaybill, now it's causing issue for `E-Invoice`, because the partner buyer details were changed from Purchase Document to Move type being a Outbound In this fix we only change Buyer-Seller Details only if it's for e-waybill Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191578
Since [1], a fix was introduced to display the actual value of a relational field instead of its ID. However, another issue occurs when a form is inside a tab (Tabs snippet) and a new tab is added. During this process, the currently active tab is cloned, including its field IDs. Although a method exists to update the IDs after cloning, the form rendering is triggered beforehand. This causes the labels property of input elements—which is expected to return a NodeList of associated <label> elem
Original PR description
Since [1], a fix was introduced to display the actual value of a relational field instead of its ID. However, another issue occurs when a form is inside a tab (Tabs snippet) and a new tab is added.…
Since [1], a fix was introduced to display the actual value of a relational field instead of its ID. However, another issue occurs when a form is inside a tab (Tabs snippet) and a new tab is added. During this process, the currently active tab is cloned, including its field IDs. Although a method exists to update the IDs after cloning, the form rendering is triggered beforehand. This causes the labels property of input elements—which is expected to return a NodeList of associated <label> elements—to fail because the cloned input IDs are not unique. This commit resolves the issue by using querySelector to target the associated label elements directly. Steps to reproduce: - Open the Website editor. - Drag & Drop a Tabs snippet. - In the first tab, drag & Drop a Form snippet. - Set the first field as a radio buttons. - Make the second field's visibility depend on the first field. - Add a new tab by clicking the "+" icon in the right panel. - Observe that a traceback occurs. A second issue related to [1] has been resolved for cases where there is only a single checkbox. In this scenario, the value displayed in the visibility condition dropdown menu should be "Yes". opw-4345340 [1]: https://github.com/odoo/odoo/commit/4b37f22cece5424d6992c6bafe619c9a457d184b Forward-Port-Of: odoo/odoo#190460
Israel is raising VAT rate from 17% to 18% on 1/1/2025. Changes: Added new taxes (17% -> 18%) Archived 17% taxes Added tax group (VAT 18%) Modified fiscal position to match those taxes Modified VAT report to include VAT Inputs 18% Updated default tax ids for IL res.company Backward-Port-Of: https://github.com/odoo/odoo/pull/191209 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191749
Original PR description
Israel is raising VAT rate from 17% to 18% on 1/1/2025. Changes: Added new taxes (17% -> 18%) Archived 17% taxes Added tax group (VAT 18%) Modified fiscal position to match those taxes Modified VAT report to include VAT Inputs 18% Updated default tax ids for IL res.company Backward-Port-Of: https://github.com/odoo/odoo/pull/191209 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#191749