Skip to Main Content
Status Shipped
Categories Roadmaps
Created by Bonnie Trei
Created on Oct 1, 2020

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.

  • ADMIN RESPONSE
    Sep 8, 2023

    When adding panels to dashboards, you can now choose to use the root report rather than a copy. Simply uncheck the "Create a copy" checkbox when adding a new panel. This option also applies when adding Aha! views to notes.

  • Attach files
  • Jon-Paul Ciambra
    Reply
    |
    Sep 8, 2023

    Love it! Thank you!

  • Deirdre Clarke
    Reply
    |
    Sep 7, 2023

    So great that this has shipped!
    Two questions - how does this work and how does this affect existing dashboards that I have that had their own dashboard copy of a report?

    1 reply
  • Jon-Paul Ciambra
    Reply
    |
    Aug 11, 2023

    We love our dashboards, but each time we want to make a change to the same data representation (widget) across dashboards, we have to do so for each dashboard it's used in. This causes a heavy administrative burden. Thank you!

  • Nigel Lawrence
    Reply
    |
    Jul 19, 2023

    +1 from our org....
    We use dashboards to 'template' consistent views across our product portfolios, resulting in 100s of cloned dashboards. We often have occasions where we'd like to deploy updates across this set of dashboards and today that painfully involves going into each and making the update. If we have a `deep copy` capability that allowed us to deploy updates by editing the initial source reports that would be very advantageous to us.

  • Guest
    Reply
    |
    Mar 21, 2023

    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.

  • Guest
    Reply
    |
    Nov 28, 2022

    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.

  • Karie Kelly
    Reply
    |
    May 28, 2022

    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.


  • Shannon Gupta
    Reply
    |
    Mar 25, 2022

    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. "

  • Karie Kelly
    Reply
    |
    May 18, 2021

    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.

  • +4
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...
Guest about 3 years ago in Roadmaps 1 Shipped
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 ...
Andrew Brooks about 3 years ago in Roadmaps 0 Shipped
2 MERGED

Dashboard setting to allow view changes to be applied to the panel

Merged
Currently, when you add a report view to a Dashboard, it creates a copy. The knowledge base says this is so you can customize the view in the panel without impacting the original report. I maintain audit reports for all users in Aha! and add them ...
Lindsay Zandy over 1 year ago in Reports 0 Shipped