[FIX] sales_team: fix to show team_in in partner #32045
Closed
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
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Syncing from upstream odoo/odoo (12.0)
Missing team_id in Partner view, when it's defined in the .py file Adding some logic to assign a default value when changing the Salesperson
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.
Description of the issue/feature this PR addresses:
Missing team_id in Partner view, when it's defined in the .py file
Adding some logic to assign a default value when changing the Salesperson
Current behavior before PR:
Missing team_id in Partner view
Desired behavior after PR is merged:
team_id in Partner view, with logic to assign a default value when changing the Salesperson if no vale was given by the user before
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr