In as much detail as possible, describe the problem or experience related to your idea. Please provide the context of what you were trying to do and include specific examples or workarounds:
We have product attributes that are specific to each division and allow each division to categorize the same products in different ways using a single list for each type of product attribute. We then use dependent dropdowns to map divisions to the applicable list items from each product attribute lists. In the UX, when we are filtered to a Division and have a module that shows one of our product attributes as a column, we would like the column filter to be able to show only applicable selections based on either the dependent dropdown allowed items or only items from the list that are showing in the view that is displayed. Current behavior is that all items from the full product attribute list will show in the filter and users have to scroll through a large amount of irrelevant items to their division.
How often is this impacting your users?
Very often.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
Business/end users
What would your ideal solution be? How would it add value to your current experience?
Dependent Dropdowns are able to carry over to filters OR filters limits to only items currently showing in the grid.
Please include any images to help illustrate your experience.
Using Dependent Drop down for Merch Group:
Filtering within a module that has same list as a column (shows so many irrelevant items for the specific Division selected):
