You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the current version of the module product_category_code_unique (https://github.com/OCA/product-attribute/tree/14.0/product_category_code_unique), the only restrictions available is checking that the code is unique within the whole system. However, some people might have other needs in terms of restrictions of codes. That is why I suggest improving the module in order to be able to select between different types of restrictions:
Restriction 1: Code field must be unique. If this restriction is selected, it will not be possible to have a duplicated code in the system (this is the currently available restriction).
Restriction 2: Code field cannot be duplicated in parent nodes or son nodes.
Restriction 3: Code field must be unique for product categories with the same parent category.
Only one of theseoptions could be selected and right after selecting a new option it will be checked whether the restriction can be applied or not.
If I add this feature to the module, do you think it will be interesting enough?
Thank you
The text was updated successfully, but these errors were encountered:
In the current version of the module product_category_code_unique (https://github.com/OCA/product-attribute/tree/14.0/product_category_code_unique), the only restrictions available is checking that the code is unique within the whole system. However, some people might have other needs in terms of restrictions of codes. That is why I suggest improving the module in order to be able to select between different types of restrictions:
Only one of theseoptions could be selected and right after selecting a new option it will be checked whether the restriction can be applied or not.
If I add this feature to the module, do you think it will be interesting enough?
Thank you
The text was updated successfully, but these errors were encountered: