[16.0][mig] purchase_blanket_order: Migration to 16.0 #1908
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
The default behavior in a PO is that the purchsing UoM is used as the PO line UoM when set in the product. Blanket Orders should do the same, otherwise it is a bit confusing.
…rders from date_start desc field. TT37792
Current behavior: - Create a blanket order and confirm > PBO/0001 - Convert to draft - Confirm > PBO/0001 (Previously the name was changed to another sequence PBO/0002). TT37792
…ate. Sales blanket orders had the same description, at least one of the two should change to reduce confusion.
Currently the check for assigning a new sequence is done over a translatable string, but the initial sequence name is not done being translatable, so we should make both to compare the same string. TT37792
Before this change there was the following inconsistency: - Create a blanket order. - Create a line with product A and price 1. - Confirm. - Cancel + return to draft (to be able to modify the price of the line). - Change the price to 2. - The status is automatically changed to open (without being able to modify the line). TT39646
…event inconsistencies TT39646
…etting to state open after being cancelled and edit on draft
…16.0-mig-purchase_blanket_order
53 tasks
|
@dsolanki-initos Are you still working on this PR? If so, could you add this commit please #2048 |
JordiBForgeFlow
requested changes
Jan 15, 2024
| <field | ||
| name="product_id" | ||
| context="{'partner_id':parent.partner_id, 'quantity':original_uom_qty, 'company_id': parent.company_id}" | ||
| groups="base.group_multi_company" |
There was a problem hiding this comment.
Does not make sense to add this group.
| name="original_uom_qty" | ||
| string="Original Qty" | ||
| context="{'partner_id':parent.partner_id, 'quantity':original_uom_qty, 'company_id': parent.company_id}" | ||
| groups="base.group_multi_company" |
There was a problem hiding this comment.
Does not make sense to add this group.
| <field | ||
| name="product_id" | ||
| context="{'partner_id':parent.partner_id, 'quantity':original_uom_qty, 'company_id': parent.company_id}" | ||
| groups="base.group_multi_company" |
There was a problem hiding this comment.
Does not make sense to add
| name="original_uom_qty" | ||
| string="Original Qty" | ||
| context="{'partner_id':parent.partner_id, 'quantity':original_uom_qty, 'company_id': parent.company_id}" | ||
| groups="base.group_multi_company" |
There was a problem hiding this comment.
Does not make sense to add
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.
Depends on
Web/web_action_conditionable