Skip to content

[18.0][MIG] product_operating_unit: Migration to 18.0#830

Open
hieulucky111 wants to merge 40 commits intoOCA:18.0from
komit-consulting:18.0-mig-product_operating_unit
Open

[18.0][MIG] product_operating_unit: Migration to 18.0#830
hieulucky111 wants to merge 40 commits intoOCA:18.0from
komit-consulting:18.0-mig-product_operating_unit

Conversation

@hieulucky111
Copy link
Contributor

No description provided.

mara1 and others added 30 commits July 15, 2025 16:03
Co-Authored-By: Patrick Wilson <36892066+patrickrwilson@users.noreply.github.com>
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: operating-unit-16.0/operating-unit-16.0-product_operating_unit
Translate-URL: https://translation.odoo-community.org/projects/operating-unit-16-0/operating-unit-16-0-product_operating_unit/
Currently translated at 100.0% (7 of 7 strings)

Translation: operating-unit-16.0/operating-unit-16.0-product_operating_unit
Translate-URL: https://translation.odoo-community.org/projects/operating-unit-16-0/operating-unit-16-0-product_operating_unit/es/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate.

Translation: operating-unit-16.0/operating-unit-16.0-product_operating_unit
Translate-URL: https://translation.odoo-community.org/projects/operating-unit-16-0/operating-unit-16-0-product_operating_unit/
Currently translated at 14.2% (1 of 7 strings)

Translation: operating-unit-16.0/operating-unit-16.0-product_operating_unit
Translate-URL: https://translation.odoo-community.org/projects/operating-unit-16-0/operating-unit-16-0-product_operating_unit/ja/
This PR fixes an issue with the method operating_unit_default_get
where it would return an operating unit even for a company that was
not active, which would cause all sorts of issues

Steps to reproduce on runboat,
taking as example purchase_operating_unit:

- User has a default ou belonging to Company 1
- Switch to Company 2 (make sure Company 1 is not active at all)
- Try to create a Purchase Order

The issue arises because the operating_unit field is pre-compiled
on the PO with an Operating Unit whose company is inactive,
and the onchanges cannot find or access related data.
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.