Skip to content
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

product_usability: seller_id can not be store as muti-company will be broken #214

Merged
merged 2 commits into from
Dec 12, 2024

Conversation

sebastienbeau
Copy link
Member

In multi company each company can have it own supplier with shared product, in that case supplier id are different
#211

@sebastienbeau
Copy link
Member Author

@alexis-via

@bealdav
Copy link
Member

bealdav commented May 31, 2024

Good catch

… broken

do not store the field as shared product can have different supplier
depending on the company logged
Use compute as related will always pick the first one whatever the
company logged
@sebastienbeau sebastienbeau force-pushed the 14.0-fix-product_usability branch from 1f696a7 to 0fa2024 Compare June 2, 2024 20:27
@sebastienbeau sebastienbeau merged commit 2ff3ea6 into 14.0 Dec 12, 2024
@github-grap-bot github-grap-bot deleted the 14.0-fix-product_usability branch December 12, 2024 00:39
# searching on the first line of a o2m is not that easy
# So we search all potential matching products
# Then we filter on the seller_id
records = self.search([("seller_ids.partner_id", operator, value)])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BOUM ! CRASH !
seller_ids.name and not seller_ids.partner_id

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants