Friday, March 22, 2024
4 changes · saas-17.1
Resolved issues and error corrections
Point of Sale users can now click optional products in the product information popup without encountering an error. This keeps the sales flow smoother and avoids interruptions caused by a missing action after a recent refactor.
Original PR description
Before this commit, clicking on an optional product in the product info popup would cause an error. This was due to the absence of the `setSelectedCategoryId` function, which was removed during the refactor. opw-3815392 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Creating a shift from a specific cell in the planning Gantt view now keeps the selected date instead of defaulting to the full visible calendar period. This prevents users from having to manually correct planned dates and restores the expected scheduling behavior.
Original PR description
Before this commit, when the user clicks on a gantt cell of the planning gantt view to create a shift for a specific date. By doing that, the planned dates set by default to the form view is the whole period of the gantt view instead of the date set on the gantt cell clicked. This commit removes the override erasing the default planned dates by the period of the gantt to keep the standard behavior as before.
This update resolves an issue preventing sale reports from generating correctly when multiple bank accounts were used for a payment. The previous system required a single account payment, which is now corrected. This ensures accurate reporting for all sales transactions, regardless of payment method.
Original PR description
Following commit https://github.com/odoo/odoo/commit/d9190e34543c4a1151656859acb41556bcb3a364, generating a sale report became impossible if a session had more than one account payment. This was due to a ValueError: Expected singleton. opw-3799171 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157426
This update fixes a default setting in the restaurant POS module that was incorrectly configured for US customers in the SaaS environment. Previously, the system automatically enabled tipping after payment, regardless of the user's country. This change ensures a better experience for all users by removing the US-specific default.
Original PR description
In SaaS, the DB is pre-prepared with the generic chart of accounts before the new user finishes the form. Since the default country of the generic chart of accounts is the US, then `set_tip_after_payment` option in the pre-created pos.config is set to True. Now, when the form is submitted, the country is identified but the said option remains to be True. This is a problem because not all customers are creating an odoo instance for a US company. So customers from other countries will have the option activated by default which is not a good default for them. We introduced this behavior in aa1c5b53bf131c6df96ad621e00bd2ee3d44c6c0 and in this commit we won't set the option by default anymore. Forward-Port-Of: odoo/odoo#149542