Daily updates from Odoo
Wednesday, February 13, 2019
8 changes · master
Enhancements to existing features
Users can now choose a "Last 5 Years" option when filtering date or datetime fields. This makes it easier to review longer-term trends and compare business performance across multiple years without manually setting custom dates.
Original PR description
Description of the issue/feature this PR addresses: Add "Last 5 Years" time range, to insert after Last 365 days. Current behavior before PR: Currently, There is no time range to see the data evolution over years. Desired behavior after PR is merged: Added "Last 5 Years" time range, to insert after Last 365 days. Task: https://www.odoo.com/web#id=1916017&action=327&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.e204103a3acd35269f1d986a7192e0b4 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
When duplicate contacts are merged, their loyalty points can now be added together instead of one balance being lost. This helps businesses preserve customer rewards accurately during contact cleanup and consolidation.
Original PR description
Before this commit - Loyalty points were not merging, if we merge two contacts. After this, New contact will have sum of all loyalty points of customes which are getting merged. This commit is related to task #1869488. 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
Odoo now rejects invalid rounding settings instead of returning misleading calculation results. This improves reliability in financial and sales calculations, including safer handling when currency or customer information is missing.
Original PR description
Adding two new rules to verify that invalid parameters are forbidden: * The precision_rounding must always be bigger than 0 * The precision_digits must always be equal or bigger than 0 Before this commit: * when a precision_round was 0 or smaller than 0 the float_utils functions gave as results: ** float_is_zero(0.0, precision_rounding=0.0) -> False ** float_round(1.25, precision_rounding=0.0) -> 0.0 ** float_compare(1.0, 1.0, precision_rounding=0.0) -> 1 * when a precision_digits was smaller than 0 the float_utils functions gave as results: ** float_is_zero(9.01, precision_digits=-2) -> True ** float_round(125.01, precision_digits=-2) -> 100.0 ** float_compare(121.01, 122.02, precision_digits=-2) -> 0 These results where at least not correct at worst not logic. Now, the function raises an error when the precision_rounding is smaller or equal than 0 or when the precision_digits is smaller than 0.
Demo records across sales, purchasing, repair, accounting, and website sales were updated so product descriptions better match the products shown. Purchase order lines now prefer a vendor-specific product code when available, making supplier communications clearer and reducing confusion.
Original PR description
Pad:https://pad.odoo.com/p/r.b30aef421f566d4854482088693f30ec Task:https://www.odoo.com/web?debug#id=1892754&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720
The Manufacturing app now hides operation and manufacturing readiness options when a bill of materials is set up as a kit, since those settings do not apply. The help text is also made easier to understand, reducing confusion for users configuring kits.
Original PR description
Task : https://www.odoo.com/web?debug=assets#id=1929631&action=327&model=project.task&view_type=form&menu_id=4720 Pad : https://pad.odoo.com/p/r.250cb4e677684d1e8732345ac3490013 Current behavior before PR: 1) https://drive.google.com/a/odoo.com/file/d/1GzRFc8xKiVDcnKfPkXJirVHzmYXI4CGU/view?usp=drivesdk 2) https://drive.google.com/a/odoo.com/file/d/1vmQ3uHd478Cq9TB-NS6eEYNIceVt9jVh/view?usp=drivesdk Desired behavior after PR is merged: https://www.awesomescreenshot.com/image/3831254/aff4d6dd023a06ade890b9bacead8f43 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This update clarifies how public and logged-in slide views are counted, making eLearning statistics more reliable. It also fixes course member counting and tightens upload/publish permissions so training content is managed by the right responsible users.
Original PR description
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
This fixes a bank synchronization issue that could stop online bank statements from processing when a journal did not have a specific currency set. Businesses can now use optional journal currency settings without disrupting bank statement synchronization.
Original PR description
Before this commit, the online_sync_bank_statement wasn't working correctly. This occurs when the currency was not defined in the journal (currency is optional in journal). Indeed, when you call the float_is_zero function with the currency's precision (0 as it's not defined) an error is raised. Now we take into account if currency is defined.
Code cleanup and technical improvements
The Documents app now uses Odoo's shared search panel instead of a custom folder and tag selector. This makes navigation more consistent with other parts of Odoo and reduces custom code, helping future improvements and maintenance.