Tuesday, December 24, 2024
8 changes · 17.0
Enhancements to existing features
The point of sale pricelist button was adjusted so its list of available pricelists can be customized more easily. This makes it simpler for future extensions to filter pricelists for specific business needs without changing the main button behavior.
Original PR description
Splitting the function `click` on the Pricelist Button to make it inheritable, by creating a new function called `getPricelistList` that will allow filtering them whenever needed. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
The French POS certification module now shows the old unit price correctly on the products screen. This helps cashiers and customers see price changes clearly and avoids confusion during sales.
Original PR description
Description of the issue/feature this PR addresses: Current behavior before PR: The "Old unit price" text in the POS products screen is not showing properly when the l10n_fr_pos_cert is installed. Desired behavior after PR is merged: The "Old unit price" text will be showing up properly using simular code to what is on https://github.com/odoo/odoo/blob/a0ab0ce39bf4cba5e90eae109bcd006b39e31c6c/addons/l10n_fr_pos_cert/static/src/xml/OrderReceipt.xml#L14 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
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
Changing the customer on an invoice now correctly updates the assigned sales team. This prevents invoices from being left with the wrong or missing sales team, keeping reporting and ownership consistent with sales orders.
Original PR description
Versions 16.0+ Description of the issue/feature this PR addresses: The issue occurs when selecting a partner in an invoice, the sales team is not correctly computed. The problem arises because the…
Versions 16.0+ Description of the issue/feature this PR addresses: The issue occurs when selecting a partner in an invoice, the sales team is not correctly computed. The problem arises because the default_team_id is not passed as a parameter to the context when the partner is selected, which works correctly in sales orders but fails in invoices. Current behavior before PR: When modifying the partner_id in an invoice, the sales team is not recomputed, leading to incorrect or missing sales team assignment. Desired behavior after PR is merged: After this PR is merged, modifying the partner_id on an invoice will correctly recompute the sales team by passing the default_team_id in the context, ensuring consistent behavior between invoices and sales orders. I will now provide a short video demonstrating the error. This issue is replicable if none of the sales teams have any members assigned. https://drive.google.com/file/d/15mUpXvdlVpGZXW976PK7EVYH6X4sm2CJ/view?usp=sharing PR of v16 https://github.com/odoo/odoo/pull/180961
This fix prevents database upgrades from crashing when the mail app encounters a field that has already been removed from the system. It helps ensure smoother upgrades and reduces manual recovery work for affected databases.
Original PR description
I encountered an error when upgrading the database. This error is because the `fname` does not exist in `self._fields` after the field has been removed in the code. Here is all the traceback : ```…
I encountered an error when upgrading the database.
This error is because the `fname` does not exist in `self._fields` after the field has been removed in the code.
Here is all the traceback :
```
Traceback (most recent call last):
File "/home/do/my_projects/odoo-17/odoo17/odoo/service/server.py", line 1313, in preload_registries
registry = Registry.new(dbname, update_module=update_module)
File "<decorator-gen-16>", line 2, in new
File "/home/do/my_projects/odoo-17/odoo17/odoo/tools/func.py", line 87, in locked
return func(inst, *args, **kwargs)
File "/home/do/my_projects/odoo-17/odoo17/odoo/modules/registry.py", line 113, in new
odoo.modules.load_modules(registry, force_demo, status, update_module)
File "/home/do/my_projects/odoo-17/odoo17/odoo/modules/loading.py", line 536, in load_modules
env['ir.model.data']._process_end(processed_modules)
File "/home/do/my_projects/odoo-17/OpenUpgrade/openupgrade_framework/odoo_patch/odoo/addons/base/models/ir_model.py", line 77, in _process_end
return IrModelData._process_end._original_method(self, modules)
File "/home/do/my_projects/odoo-17/odoo17/odoo/addons/base/models/ir_model.py", line 2558, in _process_end
self._process_end_unlink_record(record)
File "/home/do/my_projects/odoo-17/odoo17/odoo/addons/base/models/ir_model.py", line 2487, in _process_end_unlink_record
record.unlink()
File "/home/do/my_projects/odoo-17/odoo17/addons/mail/models/ir_model_fields.py", line 52, in unlink
'sequence': self.env[field.model_id.model]._mail_track_get_field_sequence(field.name),
File "/home/do/my_projects/odoo-17/odoo17/addons/mail/models/models.py", line 181, in _mail_track_get_field_sequence
if isinstance(fname, IrModelFields):
KeyError: 'date_process'
```
close: https://github.com/odoo/odoo/issues/172891
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis update removes a confusing display option for service products within the product catalog. Previously, users could see 'View Availability,' which wasn't relevant for service products. This change simplifies the user experience and ensures users only see options that apply to their needs.
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#58817
Backport commit 454f861 by @svs-odoo. Versions affected: - 16.0 - 17.0 Before this commit, the `product.template` constrains `_check_sale_product_company` didn't work if the recordset contains products from different companies, causing a traceback. How to reproduce: - Create multiple products at once in different companies. For example, in the shell of a newly created DB: - company_b, company_a = self.env["res.company"].search([]) - products = self.env["product.product"].create([ {'n
Original PR description
Backport commit 454f861 by @svs-odoo.
Versions affected:
- 16.0
- 17.0
Before this commit, the `product.template` constrains `_check_sale_product_company` didn't work if the recordset contains products from different companies, causing a traceback.
How to reproduce:
- Create multiple products at once in different companies. For example, in the shell of a newly created DB: - company_b, company_a = self.env["res.company"].search([]) - products = self.env["product.product"].create([ {'name': "prod1", 'company_id': company_a.id}, {'name': "prod2", 'company_id': company_b.id}]) -> Traceback.
To fix this issue, this commit groups products by their company in `_check_sale_product_company`.
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#191522Issue: In the task action view of the sale order, the task ID is passed in the action domain, which results in showing only old tasks. Newly created tasks are not visible because their IDs are not included in the domain. Solution: Instead of passing task ids, we now check for project_id, sale_order_id, or sale_line_id to ensure the new tasks are properly displayed. Steps to Reproduce: - Install the sale_project module. - Create a Sale Order (SO). - Add a product con
Original PR description
Issue: In the task action view of the sale order, the task ID is passed in the action domain, which results in showing only old tasks. Newly created tasks are not visible because their IDs are not included in the domain. Solution: Instead of passing task ids, we now check for project_id, sale_order_id, or sale_line_id to ensure the new tasks are properly displayed. Steps to Reproduce: - Install the sale_project module. - Create a Sale Order (SO). - Add a product configured to create a project with tasks. - Click on the "Tasks" smart button from the SO. - Go to the Kanban view. - Create a new task and give a name. - Reload the page. - Check if the task is visible (the issue was that new tasks were not visible). Affected PR: https://github.com/odoo/odoo/pull/135771/files task-4224564 Forward-Port-Of: odoo/odoo#184879