Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[17.0][MIG] sale_pricelist_global_rule: Migration to version 17.0 #3526

Open
wants to merge 8 commits into
base: 17.0
Choose a base branch
from

Conversation

carlos-lopez-tecnativa
Copy link
Contributor

  • Reused Odoo's base code for computing pricelists, adapted it to new functions, and simplified the logic.
  • Renamed selection options for the applied_on field: 4_global_product_template to 3_1_global_product_template and 5_global_product_category to 3_2_global_product_category to ensure the correct order in pricelist items.
  • Fixed an assertion in the tests. Previously, changing the UoM did not update the price, but this behavior was introduced in PR [16.0][MIG] sale_order_qty_change_no_recompute: Migration to version 16.0 #2473.
  • Added a new assertion for the pricelist_item_id field.

TT52357
@Tecnativa @pedrobaeza @victoralmau could you please review this.

carlos-lopez-tecnativa and others added 6 commits January 8, 2025 14:12
… quantities across sales order lines

- by product template
- by product category
…onstraint conflicts

The `product_variant_default_code` module adds a unique constraint, which causes test failures when installed alongside `sale_pricelist_global_rule`. This fix adjusts the tests in to avoid conflicts with this unique constraint, ensuring compatibility when both modules are installed.
If not, we get:

```
Traceback (most recent call last):
  File "/opt/odoo/custom/src/odoo/odoo/http.py", line 658, in _handle_exception
    return super(JsonRequest, self)._handle_exception(exception)
  File "/opt/odoo/custom/src/odoo/odoo/http.py", line 301, in _handle_exception
    raise exception.with_traceback(None) from new_cause

psycopg2.errors.DatatypeMismatch: ARRAY types integer and boolean cannot be matched

LINE 9: ...L OR item.global_product_tmpl_id = any(ARRAY[false,...
```

A little refactor for better code in the method is also done.

TT51677
- Reused Odoo's base code for computing pricelists, adapted it to new functions, and simplified the logic.
- Renamed selection options for the applied_on field: 4_global_product_template to 3_1_global_product_template and 5_global_product_category to 3_2_global_product_category to ensure the correct order in pricelist items.
- Fixed an assertion in the tests. Previously, changing the UoM did not update the price, but this behavior was introduced in PR OCA#2473.
- Added a new assertion for the pricelist_item_id field.
@pedrobaeza
Copy link
Member

CI is red

@pedrobaeza
Copy link
Member

/ocabot migration sale_pricelist_global_rule

@OCA-git-bot OCA-git-bot added this to the 17.0 milestone Jan 8, 2025
@OCA-git-bot OCA-git-bot mentioned this pull request Jan 8, 2025
84 tasks
@carlos-lopez-tecnativa carlos-lopez-tecnativa force-pushed the 17.0-mig-sale_pricelist_global_rule branch from 5c871a9 to 58dcdfe Compare January 9, 2025 12:06
@carlos-lopez-tecnativa
Copy link
Contributor Author

CI is red

I found an issue in this PR: OCA/sale-workflow#3150. Please let me know if it’s okay to add this commit to the current PR or if I should create a new, independent PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants