[16.0] [MIG] sale_order_rename: Migration to 16.0#4378
Open
pcastelovigo wants to merge 13 commits into
Open
Conversation
BhaveshHeliconia
approved these changes
Jun 5, 2026
Contributor
BhaveshHeliconia
left a comment
BhaveshHeliconia
left a comment
There was a problem hiding this comment.
Functional review LGTM!
pcastelovigo
force-pushed
the
16.0-pr-3556-sale-order-rename
branch
2 times, most recently
from
8789a7d to
14d1eec
Compare
Rewrite check for unique sale.order name, using api.constraint and ensure that name is unique on same company. Update test according to new name uniqueness check logic Remove xpath for sale order name label because the form is always in edit mode
pcastelovigo
force-pushed
the
16.0-pr-3556-sale-order-rename
branch
from
14d1eec to
b859e4c
Compare
OCA-git-bot
added
the
mod:sale_pricelist_display_surcharge
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 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.
Same as #3556 with the changes requested by @alexey-pelykh
Functional test on my side