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:
Polaris specific
Use case: In classic we stage lists to only have the nodes with numbers being created (e.g. Customer_account) to populate the model, but polaris enables us to have all possible list member combinations in the model (instead the dimension would be customer, Accounts).
For senior team members this is not an issue as they know the nodes of Region/Customer/account mapping that should have output. But for a new person/or model builder it would be handy to have only output options based on the selection of a "main" driver.
How often is this impacting your users?
Anytime I have a large combination of items and few cells with numbers. It would be ok if I only had X- & Y-Axis but when you have more than 6 dimensions it becomes very hard to manage.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
Model builders who does not recognise the dimensions meaning, End users.
What would your ideal solution be? How would it add value to your current experience?
Suppress Zero with the option to apply a "driver dimension" on the UX. This dimension have free selection. Any other driver only show output for this selected item, if I update a second selectos, the remaining selectors should then be dependent on selector 1 & 2, and so it continues.
Change of dominant driver behavior?
Each time the dominant driver dimension is updated, the UX selectos goes blank if there is no underlying hit again. (meaning if i have values on A and B for a selector combination then the Native selectors stay the same, but if C would be 0 and I applied C instead, then I would have to configure the settings again).
Any improvement on this topic would be useful!
