We’re at the phase in our deployment where I have been setting up an enormous number of dashboards. One thing I have noticed is that Dashboards are presented all as one “screen”, so that you would need to scroll to view all content in a particularly large dashboard.
I would find it more convenient if there were an option to set up “pages” of a dashboard, and optionally to have the pages auto-transition/carousel through the pages. For example, I have a couple dashboards that show overall statistics for our manufacturing line:
Qty of each product built per day + over the week
Yields of inspected materials off of the line
Engineering data and control charts for a couple specific products.
Instead of having that on three dashboards I have to switch between, I’d rather just have 1 dashboard with three “pages” that could carousel throughout the day.
Optional:
If a “page” display mode is made available, it would be nice to include the option to frame analytics height relative to screen, and not just width vis-a-vis columns. That way when I create a dashboard for display on different-sized monitors, I can reliably know the items will all display at the same proportions.
Thanks for the suggestion here. I can see how this would help with organization and display of your dashboards, especially with so many!
One initial thought, is that you could put the 3 dashboard you would like to display together in an app. But I’m curious to understand more why you would prefer to have things organized on the dashboard page instead?
The big thing is to easily be able to display the set of dashboards to other users, or keep open in another screen. Currently, if I wanted to have a wallboard that showed the data, I would need to either cram everything onto one dashboard, or open multiple dashboards in different tabs, and use keyboard automation to ctrl+tab through each tab. If I could paginate and carousel dashboards with the native dashboard built-ins, then I could instead just manage one tab without needing external software.
While I could also do this with an app using a timed trigger, since we are a GxP company the board would need to be periodically jogged to ensure it does not automatically turn off, in addition to using a license simply to run a wallboard.
Thank you for outlining this use case so clearly— The challenges you mentioned, like having to cram everything into one dashboard or rely on external automation for tab cycling, are definitely areas where we can do better. Native pagination aligns with our goals of improving usability and reducing the need for workarounds across the platform.
We’re exploring how improvements in this area could align with our future plans, as it’s clear this would be a valuable feature. If anyone else in the community has similar needs or additional suggestions, please share or upvote this post—as it helps us understand the demand and prioritize accordingly. Thank you again for bringing this up, and keep them coming
