Item groups can have multiple trees with multiple root nodes.
They are used to classify products under sales, purcahses etc but also on what is displayed on the website, if this functionality is used.
This double function may cause some unambiguity. Because: under Item definition only One (1) end node can be selected whereas under website multiple endnodes or even groups can be defined
If a user enters a new Item, he should now which end nodes are used for the Item definition and which for website display.
May be it would be a solution the have a seperate “show in website” classification tree/list, that than is also listed under Website (and not under Stock as is now the case)
If under dataentry the whole tree would become visible (this would enhance usuability anyway) than we could make two roots: internal_item_classification and Web_item_classification preventing misstakes.
robert