[16.0][MIG] procurement_purchase_no_grouping: Migration to 16.0 #2186
Conversation
This file contains 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
|
/ocabot migration procurement_purchase_no_grouping |
pedrobaeza
reviewed
Mar 4, 2024
…ion to avoid problems on other searches made on same method
… README [ADD] icon.png
pre-commit update
Currently translated at 100.0% (8 of 8 strings) Translation: purchase-workflow-13.0/purchase-workflow-13.0-procurement_purchase_no_grouping Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-13-0/purchase-workflow-13-0-procurement_purchase_no_grouping/zh_CN/
When purchase grouping is set to no order grouping, the previously returned domain ensured no other PO is found, but being the same domain for all will make that they are grouped together in a batch operation, like the creation of all procurements from a confirmed sales order. Steps to reproduce: * Create 2 products with MTO and different vendors. * Add both in a sales order. * Confirm the sales order. * One purchase order is created for both products instead of 2, more even in this case that they have different vendors. Fixes OCA#975
procurement_purchase_no_grouping 13.0.2.0.0
…red_purchase_grouping field procurement_purchase_no_grouping 13.0.3.0.0
Steps to reproduce: - Create a product with MTO route and "No line grouping" product category. - Create an SO with such product and quantity = 1. - Confirm it. - A purchase order is created with such product and qty = 1. - Edit the sales order, and change quantity = 2. Current behavior: A new purchase line is created with quantity = 2, having ordered 3 units instead of 2. Expected behavior: The same existing purchase line is updated with quantity = 2. ------ For solving this problem, we are going to group by procurement group instead of simply discarding any possible line grouping. NOTE: This makes that if you manually assign the same procurement group to several different sales orders, the grouping will be done no matter the grouping criteria, but this is the only way to do it without having to put a lot of glue modules, and on standard operation mode, procurement groups are not reused between sales orders. TT33031
[UPD] Update procurement_purchase_no_grouping.pot [UPD] README.rst
Currently translated at 5.8% (1 of 17 strings) Translation: purchase-workflow-15.0/purchase-workflow-15.0-procurement_purchase_no_grouping Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-procurement_purchase_no_grouping/pt_BR/
procurement_purchase_no_grouping 15.0.1.0.1
Currently translated at 5.8% (1 of 17 strings) Translation: purchase-workflow-15.0/purchase-workflow-15.0-procurement_purchase_no_grouping Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-procurement_purchase_no_grouping/it/
Currently translated at 100.0% (17 of 17 strings) Translation: purchase-workflow-15.0/purchase-workflow-15.0-procurement_purchase_no_grouping Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-procurement_purchase_no_grouping/es/ [UPD] README.rst Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: purchase-workflow-15.0/purchase-workflow-15.0-procurement_purchase_no_grouping Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-procurement_purchase_no_grouping/
- Include context keys for avoiding mail operations overhead. [BOT] post-merge updates
Currently translated at 100.0% (17 of 17 strings) Translation: purchase-workflow-15.0/purchase-workflow-15.0-procurement_purchase_no_grouping Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-procurement_purchase_no_grouping/es/
[UPD] Update procurement_purchase_no_grouping.pot [BOT] post-merge updates Update translation files Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: purchase-workflow-15.0/purchase-workflow-15.0-procurement_purchase_no_grouping Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-procurement_purchase_no_grouping/
Currently translated at 100.0% (16 of 16 strings) Translation: purchase-workflow-15.0/purchase-workflow-15.0-procurement_purchase_no_grouping Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-15-0/purchase-workflow-15-0-procurement_purchase_no_grouping/es/
TT46588 Co-authored-by: SoporteOperu
victoralmau
force-pushed
the
16.0-mig-procurement_purchase_no_grouping
branch
from
9b5e820 to
f17d99d
Compare
|
Changes done. |
pedrobaeza
approved these changes
Mar 4, 2024
sergio-teruel
approved these changes
Mar 5, 2024
|
/ocabot merge nobump |
|
This PR has the |
|
On my way to merge this fine PR! |
|
Congratulations, your PR was merged at 40a5c79. Thanks a lot for contributing to OCA. ❤️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Superseed #1877
Migration to 16.0
Please @pedrobaeza and @sergio-teruel can you review it?
@Tecnativa TT46588