Hi - looking to get some community input on our attempts to transition from classic dashboards to NUX.
The scenario,
A common use case we relied on in the classic dashboards was that we could apply 'select levels to show' on a list within a module, pivot that list into the page dimension and the dashboard would respect the selected levels, irrespective of if a user selected a lower or higher level of detail (either via a selector or column/row selection).
We could then use a single module with 'select levels to show' applied to give a,
- summarised view of the data (e.g. excl. lowest level of detail), with
- a subsequent view of the same module, but with the lowest level of detail shown.
The intent of these types of dashboards was to provide progressive disclosure, e.g. start with product line, before looking at individual product.
The problem,
What we're finding is that this doesn't seem to work with the NUX. If you've got dimensions in the page of a card, and you're using the same module for 2+ cards, you're at the mercy of the global selectors and you cannot independently apply selected levels to each cards page dimension (unless you turn off card sync which defeats the purpose)
I will stress that the issue is strictly the flexibility of page dimensions, as there's no way in custom/saved views to apply persistent page dimension rules on a card-by-card basis. Rows and columns seem to allow for a broader array of functionality.
What we don't want to have to do is to create new modules, but with the summary level as the list so that we can force the summary table to remain at that level or higher.
I'm hoping we've overlooked some functionality, but keen to hear your thoughts.
Cheers,
L
