Tuesday, October 29, 2024
3 changes · 18.0
Enhancements to existing features
This change improves how Odoo prepares database queries for company-specific JSON-based fields when no fallback value is defined. It enables database administrators to add targeted indexes for specific companies, which can improve performance for frequently used company-dependent data.
Original PR description
this commit changes the SQL for jsonb company dependent when fallback is not defined. The new sql allows DB managers to add index per company for some company dependent column which is not expected to be sparse. for field is not expected to be sparse 1. set index=False, company_dependent=True 2. add index per company for the result of `_field_to_sql`` e.g. `CREATE INDEX idx_name ON table USING btree (((col->'1')::float))` or `CREATE INDEX idx_name ON table USING btree (((col->'1'->>0)::varchar))` 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
The UrbanPiper point-of-sale integration now creates its discount product only when it is needed and only if it does not already exist. This reduces setup duplication and helps keep discount handling consistent without changing the day-to-day user workflow.
Original PR description
In this commit: === - Removed the XML data file for creating the discount product. - Added logic to create the discount product in Python, directly where the existing discount product is searched. - Implemented a check to first search for the discount product, and only create it if it does not already exist.
Belgian tax users can now create a payment directly while using the pay taxes wizard. This streamlines the process of paying taxes to the government and reduces the need for separate manual payment steps.
Original PR description
This commit will add the possibility to create a payment from the wizard to pay the taxes to the government. task: 4154861