[17.0][MIG] partner_delivery_zone: Migration to 17.0 #995
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
carlos-lopez-tecnativa
approved these changes
Feb 27, 2025
[IMP] partner_delivery_zone: Get delivery zone from commercial partner for non delivery contacts
- Include context keys for avoiding mail operations overhead.
The condition is modified to show the delivery zone on all prints of the report as long as it is set. TT51791
juancarlosonate-tecnativa
force-pushed
the
17.0-mig-partner_delivery_zone
branch
from
cbab6e7 to
a7da780
Compare
sergio-teruel
approved these changes
Feb 27, 2025
|
/ocabot migration partner_delivery_zone |
|
What a great day to merge this nice PR. Let's do it! |
|
Congratulations, your PR was merged at a9a5ed2. 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.
This PR replaces #769 due to inactivity.
Minimal changes
@Tecnativa TT52339
@sergio-teruel @carlos-lopez-tecnativa can you check? thanks!