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

[FIX] *: deposit product category instead of xmlid #387

Open
wants to merge 2 commits into
base: 18.0
Choose a base branch
from

Conversation

vava-odoo
Copy link
Collaborator

*beverage_distributor, micro_brewery

Before this commit, the deposit category was the one created by the industry module. A product was defined as a deposit if its category was the same one. This methodology is quite limited as it relies on the ID of the category, leading to several potentiel issues (deletion, new additional categories, ...).

This commit adds a checkbox on the product category such that any product belonging to a category with this checkbox filled is marked as a deposit product.

task-4493015

@robodoo
Copy link
Collaborator

robodoo commented Jan 21, 2025

Pull request status dashboard

@vava-odoo vava-odoo force-pushed the 18.0-deposit-category-vava branch 3 times, most recently from b1679ad to 6e8b7f5 Compare January 21, 2025 15:03
*beverage_distributor, micro_brewery

Before this commit, the deposit category was the one created by the
industry module. A product was defined as a deposit if its category was
the same one. This methodology is quite limited as it relies on the ID
of the category, leading to several potentiel issues (deletion, new
additional categories, ...).

This commit adds a checkbox on the product category such that any
product belonging to a category with this checkbox filled is marked as a
deposit product.

task-4493015
@vava-odoo vava-odoo force-pushed the 18.0-deposit-category-vava branch from 6e8b7f5 to 1bb5d94 Compare January 21, 2025 15:20
Before this commit, the analytic plan for properties was the one
created by the industry module. An account was defined as a property if
its plan was the same one. This methodology is quite limited as it
relies on the ID of the plan, leading to several potentiel issues
(deletion, new additional plans, ...).

This commit adds a checkbox on the analytic plan such that any account
belonging to a plan with this checkbox filled is marked as a property.

task-4493015
@vava-odoo vava-odoo force-pushed the 18.0-deposit-category-vava branch from 82dd3ba to c282d62 Compare January 21, 2025 16:47
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.

2 participants