-
-
Notifications
You must be signed in to change notification settings - Fork 911
[18.0][MIG] purchase_return: Migration to 18.0 #2902
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
thienvh332
wants to merge
29
commits into
OCA:18.0
Choose a base branch
from
thienvh332:18.0-mig-purchase_return
base: 18.0
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
copy of a vendor bill.
Currently translated at 100.0% (223 of 223 strings) Translation: purchase-workflow-16.0/purchase-workflow-16.0-purchase_return Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-16-0/purchase-workflow-16-0-purchase_return/it/
…eturn orders On migration commit a new display_type was introduced, 'product', but logic was not fully adapted and I was having issues when printing purchase return order report or when creating a refund. I have also added a migration script in order to restore those lines with display_type = 'product'
Currently translated at 100.0% (223 of 223 strings) Translation: purchase-workflow-16.0/purchase-workflow-16.0-purchase_return Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-16-0/purchase-workflow-16-0-purchase_return/it/
Updated by "Update PO files to match POT (msgmerge)" hook in Weblate. Translation: purchase-workflow-16.0/purchase-workflow-16.0-purchase_return Translate-URL: https://translation.odoo-community.org/projects/purchase-workflow-16-0/purchase-workflow-16-0-purchase_return/
917ddf9 to
27c4ca3
Compare
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.
Context:
purchase.orderandpurchase.order.lineto formpurchase.return.orderandpurchase.return.order.line. Over several Odoo versions, the related models have changed significantly. To avoid issues caused by outdated code, I synchronized the fields and methods betweenpurchase.return.order*andpurchase.order*for better reuse and consistency.Changes:
purchase.return.order*structures with updates frompurchase.order*across versions 16.0 → 18.0.account_idonaccount_move_lineaccording to the changes introduced in PRhttps://github.com/odoo/odoo/pull/96134.Video Demo:
https://drive.google.com/file/d/17wOZf9gEath0IErY1IhY7D6jJihiX01j/preview