RELATED IDEAS
Allow configuration of dashboards to tie panels directly to reports
Currently the only option for reports in Aha! dashboards requires creating a copy of the report. When this is done, any edits to the source report are not propagated to the dashboard panel. Some teams would prefer that the dashboard would automatically adjust with changes to the reports.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +3
2
MERGED
Updating Reports do not update Dashboards Panels
Merged
When you make updates to specific reports that drive your dashboard panels, these do not update the dashboard panels. The fix is to delete the panel and re-add the newest version of the report. This makes building dashboards much more difficult un...
1
Unlikely to implement
1
MERGED
Add a toggle to the dashboard panel that will keep the source roadmap and the panel in synch when any formatting changes happen at source
Merged
I can understand the rational of keeping formatting options between a source roadmap or pivot chart different. However there is also a good argument to want to always keep the dashboard and the source report in synch. Right now, many of our users ...
0
Unlikely to implement
I agree with other comments that refreshing the framework of the report into the dashboard should be optional. There are cases when individual reports are given to people for certain purposes, but I want to leverage that same report in a dashboard with a variety of reports. Instead of updating the source report, this feature limitation requires that I also edit the copied report in the dashboard. It would be easier to just have a SharePoint page to create my own dashboard with embedded reports than use Aha!'s dashboard functionality.
The lack of an automatic updates to reports in dashboards really devalues the concept of having a centralized dashboard, especially in a large organization. I don't understand why it can't be optional, when adding a report to the dashboard, to choose to create a unique copy or not.
As we have increased our usage of dashboards, this has become more of an issue in our maintenance, especially as our workflows evolve and we expand its usage. The volume of copies is unsustainable and we can't even tell which ones are still in use.
This is so important for us. Agree with Karie: "The value of dashboards it to provide a central point of information to gather insights, information for calls to action, etc. And folks will assume that these are not copies - when I add a report, this should be the report I navigate to and I don't want lots and lots of different reports that do the same thing - that isn't scalable and manual error will occur because your intent is to be consistent in providing the same information in the same way. "
Having this ability provides for scale across a large portfolio. The value of dashboards it to provide a central point of information to gather insights, information for calls to action, etc. And folks will assume that these are not copies - when I add a report, this should be the report I navigate to and I don't want lots and lots of different reports that do the same thing - that isn't scalable and manual error will occur because your intent is to be consistent in providing the same information in the same way. Thus, if I make a change - for example, we have a set of enterprise reports that focus on top 10 or a mid market cohort where the specific customers can change. I need to change that in each different report - not for every panel created from that report - so, remembering to change it 14 (right now) other times is open for error, misinterpretation of data, and mistrust in data when they get out of sync.