[19.0][MIG] purchase_order_type: Migration to 19.0 #2856
+12,652
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add a type of purchase orders
[FIX] bugs [FIX] in purchase_order.py [FIX] string in field purchase_type
[UPD] Update purchase_order_type.pot
* remove coding info and fix reference * added tests * add sequence is mandatory
[UPD] README.rst
Co-Authored-By: jcoux <[email protected]>
Currently translated at 21.7% (5 of 23 strings) Translation: purchase-workflow-14.0/purchase-workflow-14.0-purchase_order_type Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-14-0/purchase-workflow-14-0-purchase_order_type/fr_FR/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: purchase-workflow-14.0/purchase-workflow-14.0-purchase_order_type Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-14-0/purchase-workflow-14-0-purchase_order_type/
Currently translated at 96.1% (25 of 26 strings) Translation: purchase-workflow-14.0/purchase-workflow-14.0-purchase_order_type Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-14-0/purchase-workflow-14-0-purchase_order_type/it/
Currently translated at 42.3% (11 of 26 strings) Translation: purchase-workflow-15.0/purchase-workflow-15.0-purchase_order_type Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-purchase_order_type/pt_BR/
Currently translated at 96.1% (25 of 26 strings) Translation: purchase-workflow-16.0/purchase-workflow-16.0-purchase_order_type Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-16-0/purchase-workflow-16-0-purchase_order_type/it/
Custom sequence for an order type wasn't take in account date ranges during order creation, this fix it.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: purchase-workflow-17.0/purchase-workflow-17.0-purchase_order_type Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-17-0/purchase-workflow-17-0-purchase_order_type/
Currently translated at 100.0% (25 of 25 strings) Translation: purchase-workflow-17.0/purchase-workflow-17.0-purchase_order_type Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-17-0/purchase-workflow-17-0-purchase_order_type/it/
Currently translated at 100.0% (25 of 25 strings) Translation: purchase-workflow-17.0/purchase-workflow-17.0-purchase_order_type Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-17-0/purchase-workflow-17-0-purchase_order_type/sv/
Before this fix, when onchange event for company_id was fired, type for purchase order was always set, then sometimes overwritten, even if former order type was compatible with the new company. This cause an incompatibility with e.g. purchase_order_type_dashboard. When PO creation form is accesed coming from PO dashboard, selected order type was actually igored, because onchange for company was fired and order type overwritten. This fix it.
Currently translated at 44.0% (11 of 25 strings) Translation: purchase-workflow-17.0/purchase-workflow-17.0-purchase_order_type Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-17-0/purchase-workflow-17-0-purchase_order_type/zh_TW/
…purchase creation.
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: purchase-workflow-18.0/purchase-workflow-18.0-purchase_order_type Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-18-0/purchase-workflow-18-0-purchase_order_type/
Hudson5577
force-pushed
the
19.0-mig-purchase_order_type
branch
7 times, most recently
from
7cb6dc3 to
9c734b9
Compare
Hudson5577
force-pushed
the
19.0-mig-purchase_order_type
branch
from
9c734b9 to
89820fa
Compare
Member
|
/ocabot migration purchase_order_type |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
28 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changed 1 line in purchase_order model:
raise ValidationError(_("Document's company and type's company mismatch"))
into
raise ValidationError(self.env._("Document's company and type's company mismatch")