Monday, January 9, 2023
11 changes · master
Enhancements to existing features
Accounting users can now display the total amount in the original transaction currency even when the company currently uses only one active currency. This helps businesses distinguish older invoices, bills, and payments that were made in currencies that are no longer active.
Original PR description
…a mono-currency DB Description of the issue/feature this PR addresses: Currently, when a company is in a mono-currency environment, they can't display the total amount in currency when looking at invoices, payments, vendor bills... This could be a problem in a situation where the company currency is, for example dollars; at one point in time, transactions were made in both dollars and euros and now only the dollar currency is activated. The user wouldn't be able to differentiate between those transactions anymore. Current behavior before PR: The user can't show the total amount in currency or the currency on payments when in a mono-currency environment. Desired behavior after PR is merged: The user is able to show the total amount in currency and the currency on payments even in a mono-currency environment. task-3097112 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Point of Sale searches now always check the database for matching products and customers, even after the session has already loaded everything available. This means staff can find newly created items or customers without refreshing the POS session, improving day-to-day usability with only small extra search calls.
Original PR description
Since mid-15, when not all available-in-pos products are loaded in PoS, and they are being searched from the frontend, any matches are loaded. Currently, this feature is disabled when all such products are loaded in PoS, to avoid unnecessary call to the DB. However, if a product got created after a session and its products are loaded, it can't be loaded but with a page refresh - which can be annoying and not that user-friendly. This pr makes the load from search feature always enabled. The trade off between making a few unnecessary calls (short ones) and the inconvenience of refreshing the page once in a while, worth it. Task-id: 3092473 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The task form used in shared projects now more closely matches the standard task form used internally. This gives external project collaborators a more familiar, consistent view and adds task prioritization where relevant across project and timesheet workflows.
Original PR description
The form view of project.task in project sharing is modified to be similar to the classical form view of tasks (in backend). A prioritization is added to the views of project.task for project sharing used in the following modules: - project - sale_project - project_enterprise - hr_timesheet - sale_timesheet task-3119935
Project task sharing forms have been updated to look and work more like the standard task form used inside Odoo. This gives users a more consistent experience and adds task prioritization in shared project views across field service, timesheet, sales, and project apps.
Original PR description
The form view of project.task in project sharing is modified to be similar to the classical form view of tasks (in backend). A prioritization is added to the views of project.task for project sharing used in the following modules: - project - sale_project - project_enterprise - hr_timesheet - sale_timesheet - industry_fsm - industry_fsm_sale task-3119935 CE-https://github.com/odoo/odoo/pull/109067
Resolved issues and error corrections
Embedded list views no longer download full binary file contents unless they are actually needed. This reduces unnecessary data transfer and can make affected pages load faster, especially where dashboards or related records include file fields.
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
The Point of Sale quotations and orders button has been fixed so staff can open sales orders from the POS screen again. This restores access to quotations created in the Sales app, helping sales and checkout teams continue their normal workflow without browser errors.
Original PR description
The quotation/orders button in the POS application was not working anymore. Current behavior before PR: When pressing the button Quotations/Orders in the product screen of a POS config, the browser send an error saying that 'contexts' is undefined. Desired behavior after PR is merged: The Quotations/Orders button works again (the Quotation made in the Sales application are visible and usable from a POS config) Change made: The fix changes the import made to PosContext and the use of this import in the SaleOrderManagementScreen.js file so that the press of the SO button works as it should. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a product pricing issue that could occur when no suitable pricing rule was found. The change prevents the system from treating a product record as a price, helping avoid incorrect pricing behavior or errors in affected product workflows.
Original PR description
unprotected variable: price_type `product[False] == product` `price` should not be a product. It doesn't make any sense. Got this bug when suitable_rules is an empty record set. The fallback when no rule is found has been dropped here: https://github.com/odoo/odoo/commit/a7f30ce91766da3b9a6c97180cf97803c9de0528#diff-21fdb0b99c09254c9445e27ceee2d2e27503e93d9dd99481c010d92226db6f75R159 @Feyensv 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 update helps Croatian accounting setups migrate cleanly from older versions by aligning the Euro-based localization with the main Croatia module. It also preserves the former Kuna-based setup under a clearer name so companies can keep historical accounting data accessible.
Original PR description
To allow people from v16.0 to have the new module in EURO, we added the module l10n_hr_euro in stable, this PR modify the l10n_hr module to allow people to migrate without problem since l10n_hr_euro become l10n_hr in master. Also the old module l10n_hr of the stable version will be added so that they can keep an history. But like the other, we renamed the module to facilitate the comprehension. l10n_hr in stable become l10n_hr_kuna in master. task-id: 3102242 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Fixes an issue in Point of Sale where a temporary screen could cause a navigation-blocking overlay to cover the entire POS interface instead of only the navigation bar. This keeps protected flows safe while allowing the rest of the POS screen to remain usable as intended.
Original PR description
*: pos_hr_restaurant, pos_restaurant In #108891 the navbar was extracted out of the Chrome and into its own components, but when a temp screen is shown, an overlay is placed over the navbar to prevent the user from using it to navigate away as this can break some flows, and the overlay was not moved inside the navbar. This caused the overlay to go over the entire Chrome which was not the goal. This commit moves the block-header overlay into the navbar (and adapts some code to make the tempScreen state accessible inside the navbar).
This change prevents product pricing from using an invalid value when no suitable pricing rule is found. It helps avoid incorrect price calculations or errors in product-related workflows when pricing rules are missing or empty.
Original PR description
unprotected variable: price_type `product[False] == product` `price` should not be a product. It doesn't make any sense. Got this bug when suitable_rules is an empty record set. The fallback when no rule is found has been dropped here: https://github.com/odoo/odoo/commit/a7f30ce91766da3b9a6c97180cf97803c9de0528#diff-21fdb0b99c09254c9445e27ceee2d2e27503e93d9dd99481c010d92226db6f75R159 @Feyensv I have closed https://github.com/odoo/odoo/pull/109443 by error, can't re-open it. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The import screen now organizes field choices correctly when matching spreadsheet columns to Odoo fields. This makes imports easier and less error-prone by showing the right suggested, additional, and related fields without duplicate or confusing labels.
Original PR description
[FIX] base_import: Fix filtered fields shown in select menu During the conversion to Owl of the base_import action, the fields mapping for each column was made incorrect. The fields are now properly sorted between the suggested, additional and relational categories and the subfields are also correctly handled (no more duplicates and correct labels). (See legacy fields sorting: https://github.com/odoo/odoo/blob/16.0/addons/base_import/static/src/legacy/js/import_action.js#L759) --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr