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:
Within Polaris there is the ability to suppress cells with zeros values within the module or grid of the UX but currently there is a limitation where these setting cannot be saved. This necessitates usage of filters to limit the number of cells within saved views whereas the ability to save this suppression would natively address many use cases.
How often is this impacting your users?
Within the UX, users must enable suppression on each card and there is not currently a means for the builder to easily curate an experience where zeros are automatically suppressed from view.
This also impacts model builders when they are working with module to module import actions where the cell count of the view exceeds the allowable limit. This introduces the need for filtering which can have performance implications and increases the collateral needed to support the processes. An ability to save the view with suppression enabled would eliminate the increase speed of development and ideally be more performative.
Who is this impacting? (ex. model builders, solution architects, partners, admins, integration experts, business/end users, executive-level business users)
Model Builders and End Users
What would your ideal solution be? How would it add value to your current experience?
Similar to the export functionality (omit empty rows), I would like the ability to omit empty rows/suppress zero values on saved views. This may be an additional option in the Save As dialogue or merely saving the parameters as applied within the module which is consistent with how saving a view works for any parameter other than the suppress zero.
Additionally within the UX, I would like the ability to suppress zeros as part of the View configuration. This would allow for the default view presented to users to exclude zero values without requiring intervention on their part. Ideally users are then able to "un-suppress" or "show" blank rows if they would like to view all intersections (the inverse of the current suppress behavior).
Please include any images to help illustrate your experience.
